From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: Improving error messages
Date: 23 Mar 2003 21:33:52 +0100 [thread overview]
Message-ID: <874r5tkekv.fsf@zagadka.ping.de> (raw)
In-Reply-To: <20030323130445.GA315@gmx.de>
Wolfgang Jaehrling <pro-linux@gmx.de> writes:
> On Wed, Mar 19, 2003 at 08:48:12PM +0100, Marius Vollmer wrote:
> > Yes, very much! And even more, we don't need to keep all these
> > scm_s_expression constants. They only remove the message text from
> > the point where the message is issued. That's a minor nuisance, I'd
> > say.
>
> Thanks for the suggestion. I like the idea, but the constants are
> also declared in eval.h like this:
>
> SCM_API const char scm_s_expression[];
>
> So it seems to me like they are part of the API.
Arghh! Ok, we need to deprecate them first, but we don't need to use
them in eval.c itself.
> (However, if it ever becomes feasable to internationalize Guile to
> provide error messages in the native language of the user, this
> aspect of the API would most likely have to be changed anyway in one
> way or another.)
I guess the string constants are in the API by accident only. You
can't do anything sensible with them.
> > (I s'pose there is no problem getting "the papers" from you, right?)
>
> If I have a working and complete patch and you say that you like it,
> I'll have to contact assign@gnu.org, right?
No, you will be contacted with detailed instructions. Don't call us,
we call you! :-)
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-03-23 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 13:01 Improving error messages Wolfgang Jaehrling
2003-03-04 21:31 ` Rob Browning
2003-03-19 19:48 ` Marius Vollmer
2003-03-23 13:04 ` Wolfgang Jaehrling
2003-03-23 20:33 ` Marius Vollmer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874r5tkekv.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).