On 7/2/07, James Paige <[EMAIL PROTECTED]> wrote: > On Sun, Jul 01, 2007 at 12:29:35PM +1200, Ralph Versteegen wrote: > > > > - it's just going to cause file not > > > > found crashes all over the place, > > > > > > ... which is why I added the EXXERROR hack... :P > > > > > > > and the error messages aren't much use. > > > > > > I can't even *find* the error messages on windows, but on Linux, I have > > > found them highly helpful. I see file, function, and line number. > > > > > > > Oh, that's nice. I have to compile with -s console -exx -g and run > > with gdb to able to see and trace the error messages. All I get is > > "File not found on line 3275" > > Weird. I wonder why the error doesn't get printed on the console when > you compile with -s console
Whoops, I mean it is printed on the console with -s console, but I need a debugger to get the most from the error checking. TMC _______________________________________________ ohrrpgce mailing list [email protected] http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
