[Top][All Lists]

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

Re: [Chicken-users] ditching syntax-case modules for the utf8 egg

From: Kon Lovett
Subject: Re: [Chicken-users] ditching syntax-case modules for the utf8 egg
Date: Sun, 16 Mar 2008 07:53:32 -0700

On Mar 16, 2008, at 12:07 AM, Alex Shinn wrote:

"Kon" == Kon Lovett <address@hidden> writes:

    Kon> On Mar 15, 2008, at 9:33 AM, Felix Winkelmann wrote:

    Kon> Is this a "char-string" issue or a "byte-string"
    Kon> issue? When the source "...string..." is a string
    Kon> of ASCII non-nul char then there should be no
    Kon> problem w/ the utf8 egg overriding the string
    Kon> operators.  The problem comes when the source "..."
    Kon> is actually a "byte-string".

    Kon> I am uncomfortable with that particular Chicken
    Kon> idiom.

    Kon> How about moving the utf8 egg's
    Kon> "byte-string-srfi-13.scm" & "byte- string.scm" into
    Kon> the core? Then when a "byte-string" use is intended
    Kon> everyone will know.

That's a good idea, but they don't need to be moved into the
core, we can just split them out into a separate egg.

Since they are variable definitions the impact to the core is probably slight. But the impact on coding style is what I want. If one means string of byte say so.

Placing it in the core also means load order is not an issue.


Best Wishes,

reply via email to

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