[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Chicken-hackers] [PATCH] Small simple step towards fixing #1077: remove

From: Peter Bex
Subject: [Chicken-hackers] [PATCH] Small simple step towards fixing #1077: remove private-namespace from csi
Date: Sat, 26 Jul 2014 14:48:18 +0200
User-agent: Mutt/

Hi all,

Here's an updated version of the simple patch I wrote earlier for #1077.
It's the lowest-hanging fruit on the path towards fixing that bug.  This
patch simply removes the ugly "private-namespace" hack from the csi
program, as it doesn't need that at all.  We could make csi a module,
but I don't really see the point right now: just hiding the private
variables should be enough for now.  Later, we can determine what csi
should be exporting, if anything, and convert it into a proper module.
This should make eggs that hook into csi easier to write, if there's
an "official" API, but like I said, that's for later.

The extras unit also has the private-namespace listed as a compile-time
dependency but doesn't include it, so I've simply removed the dependency.
The srfi-69 unit gets extended with the private-namespace for no
apparent reason, so I've removed that as well.

This doesn't fix #1077 yet: for that we'd need to convert the compiler
to use the module system, as Felix proposed before, and then we'll need
to rip out the special handling for qualified symbols (best to do the
latter after making a dev snapshot, so we have something to bootstrap
from).  I will attempt to do that as well, but the csi patch is so
simple I think we can just push it without any trouble.


Attachment: 0001-Do-not-use-a-private-namespace-for-the-csi-program.patch
Description: Text document

reply via email to

[Prev in Thread] Current Thread [Next in Thread]