Re: [Chicken-hackers] read/write invariance of #!

> On Jan 13, 2019, at 2:16 PM, Evan Hanson wrote: > > > I don't think this change fixes the example you gave as a "certain > strange combination" in ticket #1572, i.e. (#! (foo bar)). ISTM that > happens because any whitespace after a "#!" token causes the reader to > skip everything until the

Re: [Chicken-hackers] read/write invariance of #!

On 2019-01-13 22:28, felix.winkelm...@bevuta.com wrote: > > Does anyone know what that's about? I can't figure out what feature that > > code is there to support. It's been there since the first check-in to > > Git (I didn't look any further back than that). > > That's intentional, to handle

Re: [Chicken-hackers] read/write invariance of #!

> I don't think this change fixes the example you gave as a "certain > strange combination" in ticket #1572, i.e. (#! (foo bar)). ISTM that > happens because any whitespace after a "#!" token causes the reader to > skip everything until the end of the line (and the same goes for a > forward

Re: [Chicken-hackers] read/write invariance of #!

Hi Jim, On 2019-01-12 10:04, Jim Ursetto wrote: > > > On Jan 11, 2019, at 9:47 PM, Jim Ursetto wrote: > > > >> On Jan 11, 2019, at 3:12 PM, Evan Hanson >> > wrote: > >> > >> In case someone decides to apply this patch, there's an unnecessary (and > >> ...) > >>