27;hook' (like COMMON-LISP:DEBUGGER-HOOK
plus COMMON-LISP:ABORT) or a REPL command would be OK with me.
I mis-type too often!
[Anyway, I could not find such a means in 2.0.0].
(2) Please provide some obvious "undefine" command, since UNINTER
Hello again,
On Thu, 17 Mar 2011, Andy Wingo wrote:
>[...]
> On Wed 09 Mar 2011 11:53, Wolfgang J Moeller writes:
>[...]
> > (define-syntax reset
> > (syntax-rules ()
> > ((_ . body)
> > (call-with-prompt 'Reset
> >(lamb
On Wed, 30 Mar 2011, Andy Wingo wrote:
> On Mon 21 Mar 2011 02:31, Wolfgang J Moeller writes:
>[...]
> > However, I don't like it anymore, since I seem to have learned
> > that this "direct implementation" doesn't at all play well
> > with the use of c
Hi,
co-routine linkage problem solved!
All it takes, is taking care that each [full] continuation
seen by one co-routine are equivalent, so it doesn't matter
which one gets saved and restored. No continuation-barrier
or dynamic-wind required!
While not obvious at first glance, doing so is easy e
user)> (string-length (symbol->string (with-input-from-string
(with-output-to-string (lambda () (display '#{a b}#)))
(lambda () (read)
$2 = 4
===
Best regards,
Wolfgang J. Moeller, Tel. +49 551 47361, wjmheenes.com
37085 Goettingen, Germany |
On Mon, 11 Apr 2011, Andy Wingo wrote:
> On Tue 05 Apr 2011 17:27, Wolfgang J Moeller writes:
>
> > scm_i_print_symbol_name() in libguile/print.c ought not insert backslashes
> > into "weird" symbol names that it prints using #{ ... }#,
> > because the "e
ut, but switch to R6RS escapes
throughout. Since there has been (in my understanding) no way to read symbols
containing "}#" so far, just keep the "transparent" treatment of those
guile-private brackets on input.
Best regards,
Wolfgang J. Moeller, Tel. +49 551 47361, wjmhee
column that's confusing me
(still with Guile V2.0.0).
Btw, meanwhile I've found that wrapping the second (macro-using) part
in another (eval ...) - thus terminating the top-level definition context -
works just fine w/o EVAL-WHEN, and so my "new" prelude now can be LOADed
into GUILE V2 independent of auto-compilation, as well as into GUILE V1, etc.
Best regards,
Wolfgang J. Moeller, Tel. +49 551 47361, wjmheenes.com
37085 Goettingen, Germany | Disclaimer: No claim intended!
http://www.wjmoeller.de/ -+ http://www.heenes.com/
< wjm: arguments allowed - WHY??
(apply abort-to-prompt continue-tag args))
[...])
Stand-alone fix:
((_ . args) ; no arguments allowed
(syntax-violation 'continue "too many arguments" x))
(_
#'(lambda () ; also, zero arguments
(abort-to-prompt continue-tag)
Best regards,
Wolfgang J. Moeller, Tel. +49 551 47361, wjmheenes.com
37085 Goettingen, Germany | Disclaimer: No claim intended!
http://www.wjmoeller.de/ -+ http://www.heenes.com/
e my code's prompt handler.
>
> I didn't mean in terms of code; I meant in terms of documentation,
> interface, expectations, etc...
Indeed. I'd like to say thanks to the authors of the new/improved GUILE manual.
Real good. E.g. finally, a description of "syntax-case&
Hi Andy,
>[...]
> On Mon 04 Apr 2011 15:05, Wolfgang J Moeller writes:
>
> > (a) to always have a well-defined result
> > (b) to allow for (break arg ...)
>
> I have implemented this in stable-2.0. It did not make it into 2.0.1
> however. Incidentally it should
bug-disable 'debug) that might
speed up execution.]
Best regards,
Wolfgang J. Moeller, Tel. +49 551 47361, wjmheenes.com
37085 Goettingen, Germany | Disclaimer: No claim intended!
http://www.wjmoeller.de/ -+ http://www.heenes.com/
Hi,
On Fri, 20 May 2011, Andy Wingo wrote:
> On Fri 29 Apr 2011 14:12, Wolfgang J Moeller 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 (appar
13 matches
Mail list logo
