From: Wolfgang J Moeller <wjm@heenes.com>
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile@gnu.org
Subject: Re: {debug,read,readline,print}-{set!,disable,enable}, etc.
Date: Sun, 22 May 2011 13:53:00 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1105221257030.17135@louix.wjm> (raw)
In-Reply-To: <m3zkmhwv7z.fsf@unquote.localdomain>
Hi,
On Fri, 20 May 2011, Andy Wingo wrote:
> On Fri 29 Apr 2011 14:12, Wolfgang J Moeller <wjm@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 symbol[s].
>
> Indeed; nasty, but it's what we've got. Fixed the docs.
Thanks.
> > [Noticed while looking for something like V1 (debug-disable 'debug)
> > that might speed up execution.]
>
> It's spelled `--no-debug'; see "Invoking Guile".
>[...]
Oops - didn't notice before at all. Thanks. Only a minor speed-up, indeed.
Invocation options ... you don't think "scheme-shell", do you?
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 ?)
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 ;-)
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.
Thanks again, best regards,
Wolfgang J. Moeller, Tel. +49 551 47361, wjm<AT>heenes.com
37085 Goettingen, Germany | Disclaimer: No claim intended!
http://www.wjmoeller.de/ -+-------- http://www.heenes.com/
next prev parent reply other threads:[~2011-05-22 11:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 13:05 shift and reset, plus "while" Wolfgang J Moeller
2011-04-13 9:47 ` Andy Wingo
2011-04-13 14:56 ` [shift and reset, plus] "while" Wolfgang J Moeller
2011-04-13 15:41 ` Andy Wingo
2011-04-13 17:31 ` Wolfgang J Moeller
2011-04-28 12:15 ` Andy Wingo
2011-04-29 12:12 ` {debug,read,readline,print}-{set!,disable,enable} Wolfgang J Moeller
2011-05-20 9:57 ` {debug,read,readline,print}-{set!,disable,enable} Andy Wingo
2011-05-22 11:53 ` Wolfgang J Moeller [this message]
2011-06-17 16:09 ` {debug,read,readline,print}-{set!,disable,enable}, etc Andy Wingo
2011-04-13 15:17 ` shift and reset, plus "while" Mark H Weaver
2011-04-28 11:10 ` Andy Wingo
2011-04-28 14:44 ` Wolfgang J Moeller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.00.1105221257030.17135@louix.wjm \
--to=wjm@heenes.com \
--cc=bug-guile@gnu.org \
--cc=wingo@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).