Re: 3 readline bugs: source positions, readline-options, endlessloop on error

2001-01-25 Thread Dirk Herrmann
On Thu, 25 Jan 2001, Martin Grabmueller wrote: Date: Thu, 25 Jan 2001 11:41:31 +0100 (MET) From: Dirk Herrmann [EMAIL PROTECTED] On Thu, 25 Jan 2001, Martin Grabmueller wrote: The next problem is that with readline, you don't get source positions in error messages. The reason

Re: 3 readline bugs: source positions, readline-options, endlessloop on error

2001-01-25 Thread Dirk Herrmann
On Thu, 25 Jan 2001, Dirk Herrmann wrote: [...] When doing this, we should also fix the code such that string ports are no problem any more. That does not seem to be possible: It seems to be a limitation of the readline library itself to only accept file ports... Best regards, Dirk

Re: 3 readline bugs: source positions, readline-options, endlessloop on error

2001-01-25 Thread Dirk Herrmann
On Thu, 25 Jan 2001, Martin Grabmueller wrote: I modified the `set-readline-*put-port!' procedures (see below), but got two questions: [...] - How can I test whether a given port is a file port? The problem is that my patch works when you pass a stupid value like #t to the procedures,

Re: 3 readline bugs: source positions, readline-options, endlessloop on error

2001-01-25 Thread Martin Grabmueller
Date: Thu, 25 Jan 2001 11:43:23 +0100 (MET) From: Dirk Herrmann [EMAIL PROTECTED] Two possible fixes came to my mind: - Check the argument in `set-readline-input-port!' and only accept valid open input ports. - When the argument check in `%readline' fails, reset the current

a bug in goops.c

2001-01-25 Thread Keisuke Nishida
I think this is a bug. --- guile-core/libguile/goops.c.~1.13.~ Thu Jan 11 16:03:18 2001 +++ guile-core/libguile/goops.c Wed Jan 24 19:19:36 2001 @@ -378,7 +378,7 @@ SCM_ASSERT (SCM_KEYWORDP (key), key, SCM_ARG1, FUNC_NAME); len = scm_ilength (l); - if (len 0 || len % 1 == 1) + if (len