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 that be possible to specify which internal string encoding is > used by the core as a CHICKEN build-time option? For embedded systems > with limited resources that will give a decent leverage to choose from - > either consume more memory but more fast lookups etc (in the case of > UCS-4) or consume less memory by the cost of UTF-8 conversions on the > fly during string operations.
I think it would be possible, but I dislike the idea because it is hard to maintain two separate compilation options like that. Cheers, Peter -- http://www.more-magic.net _______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
