[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Per-module reader, take #2

From: Neil Jerram
Subject: Re: [PATCH] Per-module reader, take #2
Date: Fri, 28 Oct 2005 22:26:07 +0100
User-agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux)

address@hidden (Ludovic Courtès) writes:

>> (`include' feels like a nice name to me.  It could be implemented
>> using an optional reader arg to load/primitive-load, something like:
>>   (include FILE) -> (load FILE (current-reader))
> Maybe `load-with-reader' is more explicit, while not as nice?  ;-)

My idea of `include' would map to `load-with-current-reader', not to
`load-with-reader'.  I would expect `load-with-reader' to require an
explicit reader argument.

We're into pretty fine details here, though!  I don't mind that much
either way.

>> And then primitive-load would call scm_frame_fluid with the optional
>> arg if supplied, SCM_BOOL_F otherwise.)
> In fact, in order to retain binary compatibility, we'd have to provide
> another function which would essentially contain the same code as
> `primitive-load' except for the optional reader argument and the default
> value of the `current-reader' fluid.

Is binary compatibility a requirement?  I presume this is aimed for
1.8, and presumably for 1.8 we'd bump libguile's major version,
wouldn't we?  (Getting into territory I don't really understand ...)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]