Hi,
Mark H Weaver skribis:
> Section 2.1 of the R7RS (draft 6) explicitly says "The #!fold-case
> directive causes the read procedure to case-fold [...] each identifier
> and character name subsequently read from the same port."
OK, this is more precise than SRFI-105, and definitely per-port (t
Section 2.1 of the R7RS (draft 6) explicitly says "The #!fold-case
directive causes the read procedure to case-fold [...] each identifier
and character name subsequently read from the same port."
Here's the relevant excerpt:
The following directives give explicit control over case folding.
l...@gnu.org (Ludovic Courtès) writes:
> Hi Mark!
>
> Mark H Weaver skribis:
>
>> l...@gnu.org (Ludovic Courtès) writes:
>
> [...]
>
>>> Of course. I just meant that, if you can call ‘make-reader’ with
>>> whatever options you’re interested in, instead of globally changing the
>>> reader’s optio
Hi Mark!
Mark H Weaver skribis:
> l...@gnu.org (Ludovic Courtès) writes:
[...]
>> Of course. I just meant that, if you can call ‘make-reader’ with
>> whatever options you’re interested in, instead of globally changing the
>> reader’s option as is currently the case, then you’re halfway throug
Hi Ludovic!
l...@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver skribis:
>> l...@gnu.org (Ludovic Courtès) writes:
>>> Mark H Weaver skribis:
>>>
I recently tried to implement reader directives, e.g.:
#!fold-case (from R7RS)
#!no-fold-case (from R7RS)
#!cur
Hi Noah,
Noah Lavine skribis:
> I might not understand this correctly, but aren't the reader flags
> only supposed to affect the specific file they're reading from? That's
> why we need a different set of reader options for each port. Of
> course, there could be one global reader that has a
> po
Hello,
On Tue, Oct 16, 2012 at 5:39 PM, Ludovic Courtès wrote:
> I think ‘current-reader’ should remove the need to have a port-to-reader
> mapping, no?
>
> Thanks for looking into this!
>
> Ludo’.
>
I might not understand this correctly, but aren't the reader flags
only supposed to affect the s
Hi Mark,
Mark H Weaver skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>> Mark H Weaver skribis:
>>
>>> I recently tried to implement reader directives, e.g.:
>>>
>>> #!fold-case (from R7RS)
>>> #!no-fold-case (from R7RS)
>>> #!curly-infix (from SRFI-105)
>>>
>>> However, I ran i
l...@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver skribis:
>
>> I recently tried to implement reader directives, e.g.:
>>
>> #!fold-case (from R7RS)
>> #!no-fold-case (from R7RS)
>> #!curly-infix (from SRFI-105)
>>
>> However, I ran into a rather serious problem. Guile's reader
Hi,
Mark H Weaver skribis:
> I recently tried to implement reader directives, e.g.:
>
> #!fold-case (from R7RS)
> #!no-fold-case (from R7RS)
> #!curly-infix (from SRFI-105)
>
> However, I ran into a rather serious problem. Guile's reader options
> are global to the entire process,
I recently tried to implement reader directives, e.g.:
#!fold-case (from R7RS)
#!no-fold-case (from R7RS)
#!curly-infix (from SRFI-105)
However, I ran into a rather serious problem. Guile's reader options
are global to the entire process, but clearly these reader directives
should a
11 matches
Mail list logo
