[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-janitors] #1274: read-all receiving #<unspecified> unless p
From: |
Chicken Trac |
Subject: |
Re: [Chicken-janitors] #1274: read-all receiving #<unspecified> unless preceded by a predicate |
Date: |
Sun, 03 Apr 2016 09:57:00 -0000 |
#1274: read-all receiving #<unspecified> unless preceded by a predicate
----------------------+--------------------
Reporter: sjamaan | Owner:
Type: defect | Status: new
Priority: major | Milestone: 4.11.0
Component: unknown | Version: 4.10.x
Resolution: | Keywords:
----------------------+--------------------
Comment (by evhan):
Transcribed from IRC: basically, {{{##sys#canonicalize-body}}} reorders
internal definitions so that multi-valued assignments always follow
normal ones. The result is always a bunch of let bindings to introduce
the vars followed by a bunch of {{{##core#set!}}} nodes to assign them,
but the normal and multi-valued var/val pairs are accumulated in
separate lists so the ordering gets lost. Then, the templating just
blindly puts the multi-valued {{{##core#sets!}}} after the others.
Currently, the "dimensions" of the lists are different, so to speak --
in the code, vars/vals gets a list of variables/expressions, whereas
mvars/mvals gets a list of lists of variables/expressions -- and
mvars/mvals has to be processed a bit more to produce a c-w-v.
--
Ticket URL: <http://bugs.call-cc.org/ticket/1274#comment:3>
CHICKEN Scheme <http://www.call-cc.org/>
CHICKEN Scheme is a compiler for the Scheme programming language.
- Re: [Chicken-janitors] #1274: read-all receiving #<unspecified> unless preceded by a predicate,
Chicken Trac <=