Re: Guile 2.0 interpretation vs compilation

2014-10-06 Thread Marko Rauhamaa
Mark H Weaver : > Alternatively, you could make sure to always compile your code, in which > case 'procedure-name' should work properly. Not a problem. Marko

Re: Guile 2.0 interpretation vs compilation

2014-10-06 Thread Mark H Weaver
Marko Rauhamaa writes: > Mark H Weaver : > >> This is expected but not ideal. Our primitive evaluator does not >> preserve non-toplevel variable names, and therefore the associated >> procedure names are lost. Maybe we can fix this in Guile 2.2. > > I noticed the issue because I have software tha

Re: Guile 2.0 interpretation vs compilation

2014-10-05 Thread Mark H Weaver
Marko Rauhamaa writes: > Mark H Weaver : > >> This is expected but not ideal. Our primitive evaluator does not >> preserve non-toplevel variable names, and therefore the associated >> procedure names are lost. Maybe we can fix this in Guile 2.2. > > I noticed the issue because I have software tha

Re: Guile 2.0 interpretation vs compilation

2014-10-05 Thread Marko Rauhamaa
Mark H Weaver : > This is expected but not ideal. Our primitive evaluator does not > preserve non-toplevel variable names, and therefore the associated > procedure names are lost. Maybe we can fix this in Guile 2.2. I noticed the issue because I have software that depends on the procedure-name of

Re: Guile 2.0 interpretation vs compilation

2014-10-05 Thread Mark H Weaver
Marko Rauhamaa writes: > Consider this program: > > ===begin test.scm=== > (define (hello) #f) > (format #t "~S\n" (procedure-name hello)) > > (define (xyz) > (define (hello) #f) > (format #t "~S\n" (procedure-name hello))) > > (xyz) > ===en