Is importC ready?
Walter Bright
newshound2 at digitalmars.com
Fri Nov 12 08:09:27 UTC 2021
On 11/11/2021 8:13 PM, Steven Schveighoffer wrote:
> While you are thinking about this, one thing I brought up in [another
> thread](https://forum.dlang.org/post/smdtv6$1rjc$1@digitalmars.com), is that the
> preprocessor automatically adds file/line information to the preprocessed file.
> That is important so you can trace the error back to the original file.
>
> But for this purpose, you do have a preprocessed file, which may have code that
> either ImportC cannot deal with or where the preprocessed file seemingly has
> been badly formed. Having to find the real line to diagnose in the real file is
> not that easy when the error messages are all based on the file/line rewrite
> tokens.
>
> It would be nice for the compiler to at least have an option to show "true"
> file/line numbers. Maybe a directive to ignore all file/line rewrite tokens.
If you really need it, running a script to delete the file/line directives would
do it.
More information about the Digitalmars-d
mailing list