another #! !# problem

another #! !# problem

[Bill Schottstaedt]

(begin
   (display 1)
#!
(display 2)
!#
)

gets:

ERROR: In procedure scm_lreadr:
ERROR: tmp34.scm:6:2: unexpected ")"
ABORT: (read-error)

whereas

(begin
#!
(display 2)
!#
   (display 1)
)

is ok.  This is the case in both the current CVS guile and version 1.6.4.



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: another #! !# problem

[Kevin Ryde]

Bill Schottstaedt <bil@ccrma.Stanford.EDU> writes:
>
> (begin
>    (display 1)
> #!
> (display 2)
> !#
> )
>
> gets:
>
> ERROR: In procedure scm_lreadr:
> ERROR: tmp34.scm:6:2: unexpected ")"

Looks like #! !# doesn't work as the last thing in a list.  Maybe that
comment should be detected and discarded in scm_flush_ws, so the
readrecparen funcs can see the close paren.


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: another #! !# problem

[Marius Vollmer]

Kevin Ryde <user42@zip.com.au> writes:

> Bill Schottstaedt <bil@ccrma.Stanford.EDU> writes:
>>
>> (begin
>>    (display 1)
>> #!
>> (display 2)
>> !#
>> )
>>
>> gets:
>>
>> ERROR: In procedure scm_lreadr:
>> ERROR: tmp34.scm:6:2: unexpected ")"
>
> Looks like #! !# doesn't work as the last thing in a list.  Maybe that
> comment should be detected and discarded in scm_flush_ws, so the
> readrecparen funcs can see the close paren.

Yes, I have done this now.

Makes me think, maybe we should remove the restriction that #! and !#
comments are only detected at the ery beginning of a line.  That
restriction serves no real purpose, imo.  Opinions?


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: another #! !# problem

[Rob Browning]

Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:

> Makes me think, maybe we should remove the restriction that #! and
> !# comments are only detected at the ery beginning of a line.  That
> restriction serves no real purpose, imo.  Opinions?

I would have thought things already worked that way, so I'd probably
be in favor of removing the restriction.  I suspect that many people
will presume that #!!# works like /**/, #||#, and other in-line
comments.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: another #! !# problem

[Marius Vollmer]

Rob Browning <rlb@defaultvalue.org> writes:

> Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:
>
>> Makes me think, maybe we should remove the restriction that #! and
>> !# comments are only detected at the ery beginning of a line.  That
>> restriction serves no real purpose, imo.  Opinions?
>
> I would have thought things already worked that way, so I'd probably
> be in favor of removing the restriction.  I suspect that many people
> will presume that #!!# works like /**/, #||#, and other in-line
> comments.

Yes.  I have made that change.

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile