Re: [Chicken-hackers] CR #1142 and upcoming changes

2014-08-20 Thread Yaroslav Tsarko
On 19.08.2014 19:24, Felix Winkelmann wrote: Sounds like a good first step, even though I personally would prefer UCS-4 strings (constant lookup + modification and so on). But that seems to be unpopular, AFAICT... Wouldn`t that be possible to specify which internal string encoding is used

Re: [Chicken-hackers] CR #1142 and upcoming changes

2014-08-20 Thread Peter Bex
On Wed, Aug 20, 2014 at 11:59:58AM +0400, Yaroslav Tsarko wrote: On 19.08.2014 19:24, Felix Winkelmann wrote: Sounds like a good first step, even though I personally would prefer UCS-4 strings (constant lookup + modification and so on). But that seems to be unpopular, AFAICT... Wouldn`t

Re: [Chicken-hackers] CR #1142 and upcoming changes

2014-08-20 Thread Felix Winkelmann
From: Peter Bex peter@xs4all.nl Subject: Re: [Chicken-hackers] CR #1142 and upcoming changes Date: Wed, 20 Aug 2014 10:02:51 +0200 On Wed, Aug 20, 2014 at 11:59:58AM +0400, Yaroslav Tsarko wrote: On 19.08.2014 19:24, Felix Winkelmann wrote: Sounds like a good first step, even though I

Re: [Chicken-hackers] CR #1142 and upcoming changes

2014-08-20 Thread Andy Bennett
Hi, The Chicken wiki still has an index of Chicken 3 eggs, although I do think chicken-setup is no longer operational. Perhaps now would be a good time to clean the wiki of vestigial references to 2 3. AIUI, this documentation is preserved for posterity and in case anyone wants to forward

Re: [Chicken-hackers] CR #1142 and upcoming changes

2014-08-20 Thread Andy Bennett
Hi, I'd love to hear from some of the people using CHICKEN in their business or for other Serious Projects (Kristian? Ivan? Andy?) how painful this would be for them. After taking some time to familiarise myself with them, these all sound like big and important changes. It took us a long

Re: [Chicken-hackers] CR #1142 and upcoming changes

2014-08-20 Thread John Cowan
Felix Winkelmann scripsit: Well, actually we might as well support several: ASCII/Latin-1, UTF-8 and UCS-2/UCS-4. Without UTF-8 it would just be a variable element-size option. But I agree that this doesn't make maintenance any easier... Let's think some more about this. We don't have to

Re: [Chicken-hackers] [PATCH 2/2] Invert poll(2) flag default

2014-08-20 Thread Moritz Heidkamp
HI Peter, Peter Bex peter@xs4all.nl writes: This seems like a good idea. However, could you also swap the two code blocks? A double negation (#ifndef NO_...) can be confusing, and by making it read #ifdef NO_POSIX_POLL (I'd probably drop the HAVE_ prefix, as that's more idiomatic