On Tue, Jan 29, 2013 at 7:26 AM, .alyn.post. <alyn.p...@lodockikumazvati.org > wrote:
> I'll throw in my two bits here. > > I'm not personally decided whether utf-8 in core would be an > improvement. I don't have enough background or knowledge of > the internals to contribute to that decision. > I know there are people who want UTF-8 in the core, but I'd rather not bring that up, because it hurts the chances of fixing SRFI-14 :) Core chicken already supports characters > 255. SRFI-14 does not, and fails badly (reporting an error instead of just #f to say the char is not in the char-set). There is no reason (philosophical, API usability, code size, runtime memory usage, runtime speed or whatever) why we shouldn't fix this. My personal recommendation (and least work for me) is to replace srfi-14 with utf8-srfi-14 (which actually has nothing to do with utf8). -- Alex
_______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
