[Swig-devel] [ swig-Bugs-469690 ] Feature request: #line directives.

[SourceForge.net <no...@so...>]

Bugs item #469690, was opened at 2001-10-09 22:09
Message generated for change (Comment added) made by wsfulton
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101645&aid=469690&group_id=1645

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Closed
Resolution: Wont Fix
Priority: 5
Private: No
Submitted By: Krzysztof Kozminski (kozminski)
Assigned to: David M. Beazley (beazley)
Summary: Feature request: #line directives.

Initial Comment:
It would be useful if the file produced by swig
included #line directives for the preprocessor, just as
the yacc/lex/flex/bison do.

This would facilitate better debugging and compilation
error reporting (in the actual input file, not in the
generated file).

KK

----------------------------------------------------------------------

>Comment By: William Fulton (wsfulton)
Date: 2010-10-03 12:16

Message:
A duplicate feature been put in at
https://sourceforge.net/tracker/index.php?func=detail&aid=1546637&group_id=1645&atid=351645

----------------------------------------------------------------------

Comment By: David M. Beazley (beazley)
Date: 2001-10-10 01:16

Message:
Logged In: YES 
user_id=7557

I tried this once before in a very early SWIG release.  It
had exactly the opposite effect---instead of making the
wrapper files easier to debug, it made them nearly
impossible to debug.  This was mainly due to the fact that
there is really not a 1-1 correspondence between the
structure of a .i file and the resulting _wrap.c file (i.e.,
each declaration in the wrap file may expand to dozens of
lines of wrapper code).  Because of this, it's very
difficult to get line numbers to track correctly (unless you
put a #line directive on every other line of the wrapper
file).  More often than not, I found that error messages
were reported for random line numbers that made no sense
whatsoever.

If we're going to do anything here, I am much more inclined
to
stick descriptive comments in the wrapper file that point
back to a specific .i file location.   Past experience
with #line was such a disaster I don't think I want to
try that again.




 


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101645&aid=469690&group_id=1645