[gambit-list] Unbound variable: ##compilation-options

Dimitris Vyzovitis vyzo at hackzen.org
Wed Jan 27 06:03:08 EST 2016


some more investigation: it is a macro module that is including
_gambit#.scm that fails:

So here is the test case for ##compilation-options:
$ gsi
Gambit v4.8.4

> (include "~~/lib/_gambit#.scm")
*** ERROR -- Unbound variable: ##compilation-options

haven't isolated the c#absent-object yet.

-- vyzo

On Wed, Jan 27, 2016 at 12:49 PM, Dimitris Vyzovitis <vyzo at hackzen.org> wrote:
> same thing with c#absent-object
>
> I have patched the bootstrap that is failing with some ugly feature
> tests, but it would be nice if these 2 objects were defined in the
> interpreter too and not just the compiler.
>
> So to summarize:
> ##compilation-options and c#absent-object are not defined in the
> interpreter and ##eval with custom expanded ##source objects fails in
> gsi because of them.
>
> -- vyzo
>
> On Wed, Jan 27, 2016 at 12:23 PM, Dimitris Vyzovitis <vyzo at hackzen.org> wrote:
>> further simple investigation shows that in gsi, ##compilation-options
>> is unbound, while in gsc it is bound to the empty list.
>>
>> On Wed, Jan 27, 2016 at 11:29 AM, Dimitris Vyzovitis <vyzo at hackzen.org> wrote:
>>> This occurs with gambit-4.8.4, when evaling a custom expander expanded source:
>>> *** ERROR IN #:case167,
>>> "/usr/local/gambit/v4.8.4/lib/_gambit#.scm"@347.38 -- Unbound
>>> variable: ##compilation-options
>>>
>>> It is a little hard to isolate a test case, but maybe this rings a bell Marc?



More information about the Gambit-list mailing list