Hi Pierre, > I have some issues concerning error-localization: > > > > 1) Bigloo is searching for /tmp/bigloo sources which seems strange for > me since I do not use this directory (even for compiling) > > Error-localization shows crappy blank lines: > > ================================================================ > 1:=> (string-append 'toto) > > File "/tmp/bigloo/runtime/Ieee/string.scm", line 2, character 25809: > #/tmp/bigloo/runtime/Ieee/string.scm<eof> > # > > LOTS OF BLANK LINES > > > > *** ERROR:string-append > Type "bstring" expected, "symbol" provided -- toto > 1:=> > > ============================================================== > > I have "fixed" this in adding a file-exists? > Even if the /tmp issue is fixed, I think it is safer to check it since you > can run your executable file on a machine without Bigloo > > ligne 745 of ./Llib/error.scm > ---------------------------------- > > (define (exception-location? e) > (with-access::&exception e (fh > e location) > (and (string? fname) (integer? location) (file-exists? fname)))) > > > > 2) I have tried to remove error-localization with the > "-gno-error-localization" and it is not working. > > Setting *error-localization* thru (option (set! *error-localization* #f)) has > no effect > > > > The generated c file is the same using -gno-error-localization or not. Yes. That's a bug of the current version. It only concerns interpreted code. Compiled code is not affected. This problem is on the very top of my todo list but I don't expect to find the time to fix it before this week-end.
Thanks again for your report. -- Manuel
