Hi all,
I noticed that an ill-placed "define-values" can still result in new
toplevel variables being defined.
In order to make this work without problems, I had to get rid of
"##core#define-toplevel" and replace it with a pure check.
Now the defining macros expand to something like this:
Hi all,
In a drive-by bugreport on IRC, it was noted that the build is broken
on NetBSD due to the newly added feature macros. This includes 4.12.0,
so I think the attached patch should go to master as well as chicken-5.
Cheers,
Peter
From 804ad0b66638d6016a2f25e8c5cad3424ff2d4aa Mon Sep 17
On Sun, Apr 02, 2017 at 09:14:01PM +0200, felix.winkelm...@bevuta.com wrote:
> I don't fully understand your remark, but the point is that the a conditional
> results in an unknown execution path. A call on the other hand may
> result in all possible things (access of the 1st def of "foo" above,
On Sun, Apr 09, 2017 at 10:26:31AM +0200, Kristian Lein-Mathisen wrote:
> Sorry about the missing subject. Here's another patch, for the
> chicken.syntax module.
Hi again,
The same comments apply to this patch as to the previous one: we don't
want to add another compilation unit to core.
> Is
On Sun, Apr 09, 2017 at 09:01:16AM +0200, Kristian Lein-Mathisen wrote:
> Hello dear CHICKEN core members,
>
> Here's my attempt at making a chicken.load module.
Hi Kristian,
Thanks for putting in some effort on CHICKEN 5! I know this is tricky
stuff to work on, so I'm glad you're taking the
Sorry about the missing subject. Here's another patch, for the
chicken.syntax module. Is this, btw, the right way to submit patches
to core?
K.
On 4/9/17, Kristian Lein-Mathisen wrote:
> Hello dear CHICKEN core members,
>
> Here's my attempt at making a chicken.load
Hello dear CHICKEN core members,
Here's my attempt at making a chicken.load module. It was fairly
straight-forward, except I don't know what to do with the unit
declaration regarding (fixnum) and (disable-interrrupts), so I copied
file.scm's:
(declare
(unit load)
(uses eval)
(fixnum) ;;