Is werror added as the constant roxen_werror when the programs are compiled for dumping purposes as well?
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2004-07-04 11:58: Subject: Re: Warnings from startup script
Stephen R. van den Berg wrote:
The check is there for a reason...
Hint: Check the macro DO_CALL_BUILTIN in interpret_functions.h. What do you think happens if s->subtype isn't FUNCTION_BUILTIN?
The logfiles are cleaner as long as those werrors aren't called...
Ok, fair enough. I'll exercise some of these, and will let you know what happens.
I tried it. You were right. It segfaults upon execution of the aliased werror. In the runtime-compiled version, it doesn't segfault. I'm not sure what this implies; that the static compiler is at fault here (indeed, the encode routine, most likely)?
The reasons why I suspect the change is correct anyway, is because:
- All we feed it is: add_constant("werror", roxen_werror);
I presume this still is correct (given that the run-time compiler works fine with it, I'd say yes). So, what needs to be fixed instead then? -- Sincerely, srb@cuci.nl Stephen R. van den Berg (AKA BuGless).
"Good moaning!"
/ Brevbäraren