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 T) [independent of > invocation-time settings] again ... (maybe via compiling to /dev/null ?) There is read-and-compile, from system base compile... > Any provision for C-style #if ... #include ... (of, say, macros > required by the subsequent code)? (LOAD) gets evaluated too late; > (INCLUDE) of definitions isn't allowed within (IF); (EVAL) again > comes too late. > (I did notice your major changes to "psyntax", but so far > I don't see how they'd help me. No problems with them either ;-) There is `eval-when', which you can use to build the exact thing you need. See "Eval When" in the manual. In the Guile context we encourage the use of modules. > Otherwise, no problems with 2.0.1. Except for a tidbit ... > > "Compiler error message not properly decoded", as in > > | moeller@louix-$ guile2 -q > | GNU Guile 2.0.1 > |[...] > | scheme@(guile-user)> (load "zwp.scm") > | ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0 > | ;;; or pass the --no-auto-compile argument to disable. > | ;;; compiling /home/moeller/scm/zwp.scm > | ;;; WARNING: compilation of /home/moeller/scm/zwp.scm failed: > | ;;; key syntax-error, throw_args (#f "definition in expression context" #f > #t dummy3) > | scheme@(guile-user)> > > where "zwp.scm" is the "prelude" snippet that I sent you on April 2. > Pretty sure it didn't look like this in 2.0.0. It might have. But fixed, in any case :-) Cheers, Andy -- http://wingolog.org/
