Re: Block comments and `read-hash-extend'

2005-06-16 Thread Kevin Ryde
[EMAIL PROTECTED] (Ludovic Courtès) writes: > > (1) This example makes Guile 1.6 and the current Guile 1.7 hang (for > some reason which I did not track down): > >guile> #! this is a comment !# (+ 2 2) >[wait forever] You mean it reads more input? >guile> #! this is

Re: dynamic argv0 relocation

2005-06-16 Thread Kevin Ryde
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes: > > That's why I added the configure option and compile switch. You do > not want this enabled for well behaved systems. Could you live with > that? I guess it's not actively harmful :-). Some configury that divined or selected the conventions of a

Re: configure.in: Look for flex

2005-06-16 Thread Kevin Ryde
[EMAIL PROTECTED] (Ludovic Courtès) writes: > > Since flex is needed when building from CVS and not needed when building > from a distribution, what about something like the following: I think AM_PROG_LEX probably does everything you need, with no explicit warning code needed. It looks like it se

Block comments and `read-hash-extend'

2005-06-16 Thread Ludovic Courtès
Hi, The patch below (1) fixes `#! ... !#' block comments and (2) allows to override them with `read-hash-extend'. (1) This example makes Guile 1.6 and the current Guile 1.7 hang (for some reason which I did not track down): guile> #! this is a comment !# (+ 2 2) [wait foreve

Re: configure.in: Look for flex

2005-06-16 Thread Ludovic Courtès
Hi, Kevin Ryde <[EMAIL PROTECTED]> writes: > No, this shouldn't be an error. The dist includes the generated C > code so you don't need lex in a normal build. > > (You need lex if you change the ".l", and in a maintainer build maybe, > so a configure check is good, but it shouldn't be an error.)