[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: read errors
From: |
Han-Wen Nienhuys |
Subject: |
Re: read errors |
Date: |
Mon, 5 Aug 2002 20:16:00 +0200 |
address@hidden writes:
> > This is not standard GNU format, but the test-suite likes the real
> > message to be in front.
>
> We need to change the test-suite, then.
OK.
> > #define INPUT_ERROR(port, message, arg) {
>
> Does this have to be a macro? I would like it better to be a function
> (like scm_misc_error) and a thinly wrapped function (like
> SCM_MISC_ERROR).
I followed the SCM_MISC_ERROR template here. BTW, is misc-error some
kind of standard, or can we have 'read-error as a key?
> > snprintf (s, 1024, "%s\nThis happened in %s%s%s line %d column %d",
> > message,
>
> Can we use scm_simple_format here? That would avoid the 1024 limit
> and would also feel more gentle since we don't need to poke into the
> strings private parts.
I'll check it out.
--
Han-Wen Nienhuys | address@hidden | http://www.cs.uu.nl/~hanwen/