"Paul D. Smith" wrote:
>
> %% nirva_at_ishiboo.com (Danny Dulai) writes:
>
> dd> On 09/27/99, esteffl_at_pbi.net said:
> >> well, I would say that the sh behaviour is a bug:-))
> >>
> >> sometime it is hard to distinguish the bug from the
> >> feature... (maybe it is indeed a bug in fvwmrc parsing, it depends
> >> on what behaviour they wanted)
>
> dd> I often use:
>
> dd> #!/bin/sh
> dd> # \
> dd> exec tclsh $0 $*
>
> dd> ... rest of script
>
> dd> or replace tclsh with perl or whatever.. The sh executes the exec
> dd> line, tclsh and everything else skips it.
>
> Just an off-topic note: as far as I know this _only_ works with Tcl. It
> definitely doesn't work with Perl, which treats backslash-newlines in
> comments just like the shell does1 (that is, ignores the backslash and
> doesn't concatenate the newline).
>
> I don't know of any other interpreter except tclsh that does it this
> way. Personally, I feel the perl/sh way is more intuitive: a comment is
> a comment, and _everything_ in a comment should be completely
> ignored... including trailing backslashes.
>
> --
>
Python.
John
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Tue Sep 28 1999 - 15:31:28 BST