On Wed 16 Nov 2011 06:00, ri...@happyleptic.org writes:
> According to the doc, guile currently maintain 3 evaluators:
>
> - the new VM
> - an evaluator written in scheme
> - the old C evaluator, used for bootstrapping the compiler.
>
> That's a lot of code just to bootstrap the compiler. Why not
-[ Wed, Nov 16, 2011 at 10:31:31AM +0100, Andy Wingo ]
> If I bootstrap Guile-X from Guile-Y, I have to make sure that Guile-X's
> code can load in Guile-Y -- not trivial -- and I have to trust the
> output of Guile-Y.
You have to make sure that the evaluator that's written in scheme
can be ru
Hi all,
Ironically, one of the LilyPond developers has been giving the Lily
parser a spring-clean, and found scm_local_eval as the answer to his
problems in the API. Unfortunately it's not just deprecated in Guile
V2, it's been totally nuked, according to NEWS.
Is there any C code from V1.8 you
On Wed 16 Nov 2011 11:17, ri...@happyleptic.org writes:
>> If I bootstrap Guile-X from GCC, I have to trust GCC.
>
> And the code for this C evaluator that's almost used nowhere thus
> probably much less tested than the rest of Guile.
On the contrary, it is used to interpret the entire compiler,
Very good then.
Forget about my remark then.
> From: Andy Wingo
> On Wed 16 Nov 2011 11:17, ri...@happyleptic.org writes:
>
>>> If I bootstrap Guile-X from GCC, I have to trust GCC.
>>
>> And the code for this C evaluator that's almost used nowhere thus
>> probably much less tested than the rest of Guile.
>
> On the contrary, it is use
-[ Wed, Nov 16, 2011 at 11:43:52AM -0800, Mike Gran ]
> I believe that you can still run the whole test suite on the C evaluator
> by erasing all the .go files from the modules lib, setting auto compile off,
> then running the check-guile script.
I though it would run the evaluator written in
