On Wed, 2005-08-10 at 17:55 -0400, R. Clayton wrote:
> There appears to be a difference between starting guile (1.6.7 on an x86
> debian
> testing system) with and without -c:
>
> $ guile
> guile> (match:substring (string-match "[0-9][0-9]" "bla987"))
> "98"
> guile> ^d
>
> $ guile -c
Marius Vollmer <[EMAIL PROTECTED]> writes:
>
> Could you try to fix this in 1.6 as well?
I put it in, I think it works.
On the merely dodgy as opposed to broken front, I suspect the hash
function should be using logxor, and that perfect-funcq doesn't need
to work the base-func into the hash, sinc
There appears to be a difference between starting guile (1.6.7 on an x86 debian
testing system) with and without -c:
$ guile
guile> (match:substring (string-match "[0-9][0-9]" "bla987"))
"98"
guile> ^d
$ guile -c '(display (match:substring (string-match "[0-9][0-9]" "bla987")))'
ERROR
On Fri, Aug 12, 2005 at 10:03:42AM +0200, Tomas Zerolo wrote:
> On Wed, Aug 10, 2005 at 04:24:47PM -0300, Jos? Roberto B. de A. Monteiro
> wrote:
> > On Wed, Aug 10, 2005 at 01:54:31PM -0400, Alan Grover wrote:
> > > I ran into this too. My reasoning was something like:
> > >
> > > The string, "/
On Wed, Aug 10, 2005 at 04:24:47PM -0300, Jos? Roberto B. de A. Monteiro wrote:
> On Wed, Aug 10, 2005 at 01:54:31PM -0400, Alan Grover wrote:
> > I ran into this too. My reasoning was something like:
> >
> > The string, "/tmp/XX" is constructed at reader time. [...]
[...]
> Thanks Alan, I thi
