Hi Julian, On Sun 23 May 2010 19:24, Julian Graham <jool...@gmail.com> 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.) > > If the fifth character is EOF instead of 'r', control is handed to > scm_read_scsh_block_comment (after ungetting EOF), which raises the > appropriate unterminated comment error. If you add a test case I'm fine with this solution; though I would prefer it to be read as #:r6rs. 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? Andy -- http://wingolog.org/
