Hi Guilers,
It might be a small thing [and of course not a priority at all], but I'd love
to see
a small evolution of the manual index structure in order to separate scheme
procedures from others, scheme variables from others...:
* Concept Index
* Scheme
Hey Neil,
On Tue 28 Oct 2008 00:51, Neil Jerram neiljer...@googlemail.com writes:
- the principle of the elisp integration is that there is a new value
#nil, which acts as EOL in list contexts, and as #f in boolean
contexts
- as one example of this, the non-VM apply accepts and handles a
Hi,
Sorry for the spam, but I'm going through some backlog that I didn't
have the resources to deal with. Has this issue been addressed?
Andy
On Sun 14 Sep 2008 14:06, Neil Jerram neiljer...@googlemail.com writes:
2008/9/12 Andy Wingo wi...@pobox.com:
On Thu 11 Sep 2008 23:06, Neil Jerram
2009/1/4 David Séverin da...@altosw.be:
Hi Guilers,
It might be a small thing [and of course not a priority at all], but I'd love
to see
a small evolution of the manual index structure in order to separate scheme
procedures from others, scheme variables from others...:
* Concept Index
Hi Neil,
On Sat 03 Jan 2009 19:38, Neil Jerram neiljer...@googlemail.com writes:
We're clearly moving towards a 2.0 release. Here is my attempt to
pull that together a bit and flesh out what needs to be done.
I think the plan is sensible.
2. The vm branch. Once the review of master is
2009/1/4 Neil Jerram neiljer...@googlemail.com:
Sorry, no. I have the code change ready to go now; do you by any
chance have a convenient test for this?
Well I worked out a test, and have now committed that + the fix to
branch_release-1-8 and master.
Neil
We're clearly moving towards a 2.0 release. Here is my attempt to
pull that together a bit and flesh out what needs to be done.
That seems like a good plan on all counts, plus perhaps
period of feature freeze on master, with testing on many OS and
architecture variants, with a special
