Re: [Chicken-hackers] [PATCH] Drop now-unnecessary exports from the "chicken.export" module

2017-06-17 Thread Peter Bex
On Sat, Jun 17, 2017 at 11:34:30AM +1200, Evan Hanson wrote: > As of afd7867, we can make these values available to the other files > that need to use them without making them part of the chicken.export > module's public API by assigning directly to namespaced identifiers. Excellent. This complet

Re: [Chicken-hackers] [PATCH] Drop now-unnecessary exports from the "chicken.export" module

2017-06-17 Thread John Cowan
On Sat, Jun 17, 2017 at 10:25 AM, Peter Bex wrote: I can imagine those macros going into (chicken base) and/or some > other modules, but a (chicken syntax) module with them in it makes > sense too. Then we could just rename (chicken syntax) on the > c-l-r page to (chicken expand) and keep expand

Re: [Chicken-hackers] [PATCH][5] FFI improvements, take two

2017-06-17 Thread Peter Bex
On Wed, Jun 14, 2017 at 09:39:13PM +0200, lemonboy wrote: > Hello hackers, > the first two patches are meant to be applied after you review them, they are > pretty much the same I've previously sent but with some minor corrections so > those should be fine now. Thanks for the patches. Attached ar

Re: [Chicken-hackers] [PATCH] Drop now-unnecessary exports from the "chicken.export" module

2017-06-17 Thread Peter Bex
On Sat, Jun 17, 2017 at 10:40:28AM -0400, John Cowan wrote: > On Sat, Jun 17, 2017 at 10:25 AM, Peter Bex wrote: > I can imagine those macros going into (chicken base) and/or some > > other modules, but a (chicken syntax) module with them in it makes > > sense too. Then we could just rename (chic

Re: [Chicken-hackers] [PATCH] Drop now-unnecessary exports from the "chicken.export" module

2017-06-17 Thread felix . winkelmann
> This brings up the obvious question: what should we do with > (chicken expand)? I was considering a patch to rename it to > (chicken syntax) like we have in c-l-r, but should we then also > rename the expand.scm file to syntax.scm? I think this would > be the most sensible thing to do. > > But

Re: [Chicken-hackers] [PATCH] Drop now-unnecessary exports from the "chicken.export" module

2017-06-17 Thread felix . winkelmann
> On Sat, Jun 17, 2017 at 10:40:28AM -0400, John Cowan wrote: > > On Sat, Jun 17, 2017 at 10:25 AM, Peter Bex wrote: > > I can imagine those macros going into (chicken base) and/or some > > > other modules, but a (chicken syntax) module with them in it makes > > > sense too. Then we could just re

Re: [Chicken-hackers] [PATCH] Fix some symbol GC issues

2017-06-17 Thread felix . winkelmann
> As Kooda found out when working on #1379, there's still some problems > with the symbol GC stuff in CHICKEN 5. Sometimes you'll see an assertion > failure in update_symbol_tables: assert(!C_persistable_symbol(sym)) will > bail out due to some symbols being released while they still had a global

Re: [Chicken-hackers] [PATCH] Drop now-unnecessary exports from the "chicken.export" module

2017-06-17 Thread Peter Bex
On Sat, Jun 17, 2017 at 07:21:30PM +0200, felix.winkelm...@bevuta.com wrote: > > I'd also like to hear what the other core members think. > > (chicken syntax), and keep expand.scm. Don't overdo it. Do you mean we rename (chicken expand) to (chicken syntax) in expand.scm (with perhaps the other ma

Re: [Chicken-hackers] [PATCH] Drop now-unnecessary exports from the "chicken.export" module

2017-06-17 Thread felix . winkelmann
> On Sat, Jun 17, 2017 at 07:21:30PM +0200, felix.winkelm...@bevuta.com wrote: > > > I'd also like to hear what the other core members think. > > > > (chicken syntax), and keep expand.scm. Don't overdo it. > > Do you mean we rename (chicken expand) to (chicken syntax) in > expand.scm (with perhap

Re: [Chicken-hackers] [PATCH] Drop now-unnecessary exports from the "chicken.export" module

2017-06-17 Thread Peter Bex
On Sat, Jun 17, 2017 at 07:57:25PM +0200, felix.winkelm...@bevuta.com wrote: > You know what? I don't know. I just realize that too many things are > changing too much, at too fast a rate. So much that I'm now totally > confused, which is an indication that perhaps this might be getting > out of ha