Hi :)
On Wed 26 May 2010 18:43, l...@gnu.org (Ludovic Courtès) writes:
>> Heh, sure. But don't make it return SCM_UNSPECIFIED, please; make it
>> treat #!r6rs as a comment. See
>> http://www.r6rs.org/final/html/r6rs/r6rs-Z-H-7.html#node_sec_4.2.3.
>
> Functions that read comments all return ‘SCM_
Hi,
Andy Wingo writes:
> On Wed 26 May 2010 15:02, Julian Graham writes:
>
We could make this more general, as the r7 committees are wont to do: if
#! is followed by whitespace or /, then read as a block comment;
otherwise read one token. In our case, we would read #!foo as #:foo
On Wed 26 May 2010 15:02, Julian Graham writes:
>>> We could make this more general, as the r7 committees are wont to do: if
>>> #! is followed by whitespace or /, then read as a block comment;
>>> otherwise read one token. In our case, we would read #!foo as #:foo. I
>>> don't think this chang
Hey Andy,
>> We could make this more general, as the r7 committees are wont to do: if
>> #! is followed by whitespace or /, then read as a block comment;
>> otherwise read one token. In our case, we would read #!foo as #:foo. I
>> don't think this change would affect anyone. What do you think?
>
>
On Sun 23 May 2010 22:52, Andy Wingo writes:
> We could make this more general, as the r7 committees are wont to do: if
> #! is followed by whitespace or /, then read as a block comment;
> otherwise read one token. In our case, we would read #!foo as #:foo. I
> don't think this change would affec
Hi Julian,
On Sun 23 May 2010 19:24, Julian Graham writes:
>> What happens with this patch if the file only contains the four
>> characters "#!r6" followed by EOF? Does it behave appropriately
>> after calling scm_ungetc on EOF? (I guess that would make it an
>> unterminated hash bang comment.
Hi Mike,
> What happens with this patch if the file only contains the four
> characters "#!r6" followed by EOF? Does it behave appropriately
> after calling scm_ungetc on EOF? (I guess that would make it an
> unterminated hash bang comment.)
If the fifth character is EOF instead of 'r', contro
> From: Julian Graham jool...@gmail.com
> One thing I noticed while look at Andreas' `wak' project is that the
> use of `#!r6rs' seems to be pretty common, which conflicts with
> Guile's support for SCSH-style block comments. Find attached a
> (somewhat inelegant) patch that adds support for the
Hello again!
> * I'm sure there are other points -- please test and reply :)
Indeed!
One thing I noticed while look at Andreas' `wak' project is that the
use of `#!r6rs' seems to be pretty common, which conflicts with
Guile's support for SCSH-style block comments. Find attached a
(somewhat in
Hi,
On Fri 21 May 2010 14:47, Julian Graham writes:
>> * The R6RS specifies many situations in which a conforming
>> implementation must signal a specific error. Guile doesn't really
>> care about that too much -- if a correct R6RS program would not hit
>> that error, we don't bother chec
Hey Andy,
> * The R6RS specifies many situations in which a conforming
> implementation must signal a specific error. Guile doesn't really
> care about that too much -- if a correct R6RS program would not hit
> that error, we don't bother checking for it.
In a lot of these cases, that's b
11 matches
Mail list logo
