public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Stephen Crawley <crawley@dstc.edu.au>
To: abies@pg.gda.pl
Cc: mauve-discuss@sources.redhat.com, crawley@piglet.dstc.edu.au
Subject: Re: 600+ BigDecimal tests
Date: Mon, 20 Jan 2003 02:11:00 -0000	[thread overview]
Message-ID: <200301200210.h0K2Asfh007156@piglet.dstc.edu.au> (raw)
In-Reply-To: Message from Artur Biesiadowski <abies00@wp.pl>  of "Mon, 20 Jan 2003 02:21:16 +0100." <3E2B4F0C.7010205@wp.pl>

> Stephen Crawley wrote:
> 
> > BTW.  Has this question been debated / decided in the past?  The reason
> > I ask is that application code may rely on exception message strings to 
> > discriminate exception cases.  IMO, this is a BAD THING (tm), but in some
> > cases, the application programmer may have little choice.
> 
> This is doomed to failure from very start. Exception strings generated 
> by system should be localized (so they can be shown to user in worst 
> case). So there is no way to write language-portable program which looks 
> at details of exception messages.

True ... but this doesn't stop programmers doing this kind of thing out of
ignorance or desperation.  Still, I'm convinced that there is little value
in busting a gut to get identical exception messages.

-- Steve

  reply	other threads:[~2003-01-20  2:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-22 14:58 Anthony Green
2003-01-03  1:35 ` Mark Wielaard
2003-01-17 19:26   ` Mark Wielaard
2003-01-18 15:27     ` Dalibor Topic
2003-01-18 16:05       ` Mark Wielaard
2003-01-19 23:40         ` Stephen Crawley
2003-01-20  0:09           ` Anthony Green
2003-01-20  0:25             ` Stephen Crawley
2003-01-20  1:21               ` Artur Biesiadowski
2003-01-20  2:11                 ` Stephen Crawley [this message]
2003-01-20  9:48             ` Dalibor Topic
2003-01-20  0:06   ` Anthony Green

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200301200210.h0K2Asfh007156@piglet.dstc.edu.au \
    --to=crawley@dstc.edu.au \
    --cc=abies@pg.gda.pl \
    --cc=crawley@piglet.dstc.edu.au \
    --cc=mauve-discuss@sources.redhat.com \
    /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).