[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 3 readline bugs: source positions, readline-options, endless loop on
Re: 3 readline bugs: source positions, readline-options, endless loop on error
Thu, 25 Jan 2001 11:41:31 +0100 (MET)
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 is that the readline port created by
> `make-readline-port' (readline.scm) is not given a file name. The
> following patch fixes the problem for simple cases, but not when
> calling `set-readline-input-port!', which should also copy the
> filename; but I am not sure how to test this procedure.
> Maybe this problem is not worth fixing anyway, because the filename is
> always `standard input'.
I think the problem has to be solved differently: Why should the output
of source positions be dependent of the existence of a filename for an
input port? This does not make sense, for example for string ports.
Thus, I suggest to display source positions independent of whether the
port has an associated file name. If no file name was given, the error
message can use a default string like "<unnamed port>". Or, rather one
could think of storing the port with the source properties instead of a