Re: {debug,read,readline,print}-{set!,disable,enable}, etc.

2011-06-17 Thread Andy Wingo
Hi Wolfgang, On Sun 22 May 2011 13:53, Wolfgang J Moeller w...@heenes.com writes: As regards (primitive-load) - it's only after our discussion that I realized that without file-compilation GUILE seems to always (slowly) interprete the LOADed code. Makes me ask for LISP's (LOAD ... :COMPILING

Re: {debug,read,readline,print}-{set!,disable,enable}, etc.

2011-05-22 Thread Wolfgang J Moeller
Hi, On Fri, 20 May 2011, Andy Wingo wrote: On Fri 29 Apr 2011 14:12, Wolfgang J Moeller w...@heenes.com writes: In fact, {debug,print,read}-set! are macros that want option-name to be a literal symbol, while {debug,read}-{en,dis}able are procedures indeed (apparently taking multiple

Re: {debug,read,readline,print}-{set!,disable,enable}

2011-05-20 Thread Andy Wingo
On Fri 29 Apr 2011 14:12, Wolfgang J Moeller w...@heenes.com writes: In fact, {debug,print,read}-set! are macros that want option-name to be a literal symbol, while {debug,read}-{en,dis}able are procedures indeed (apparently taking multiple arguments) that want the option-name[s] to be quoted