Re: [Chicken-hackers] [PATCH] Fix a logical bug in the optimizer

[Peter Bex]

On Mon, Mar 27, 2017 at 08:37:05PM +0200, lemonboy wrote:
> As promised here's the patch, sorry for the noise.

I don't understand this code at all.  Why does it (touch) and then
scan the first expression again, and what does "escaped" mean exactly?

Besides, why does touch reset "previous" completely?  IIUC, this would
mean something like the following results in keeping all the preceding
definitions:

(set! foo 1)
(if (read) (print "read something") (print "read false"))
(set! foo 2)

The same with any procedure call, right?

Also, should this also treat the newly added "define-toplevel" core
expression like it treats set!?

Cheers,
Peter

signature.asc
Description: Digital signature