Jeff Clites <[EMAIL PROTECTED]> wrote:

> I'd really like a way to turn them off easily (for the ops as well,
> actually). I find them to be counterproductive (for our stuff), since
> what gets shown in the debugger isn't stuff you can actually get gdb to
> evaluate.

It depends. While hacking PMC files its much more useful to have the gcc
error line within the pmc files. Debugging ops is sometimes more
intuitive, if you see the corresponding .c file in the debugger, but not
always.

Anyway, as $ENV{PARROT_NO_LINE} is already in ops2c.pl, it should be
present in all build tools.

> JEff

leo

Reply via email to