From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,699cc914522aa7c4 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!wns13feed!worldnet.att.net!208.49.83.154!uns-out.usenetserver.com!news.usenetserver.com!pc03.usenetserver.com!news.flashnewsgroups.com-b7.4zTQh5tI3A!not-for-mail Newsgroups: comp.lang.ada Subject: Re: Structured exception information References: From: Stephen Leake Date: Wed, 24 Jan 2007 21:32:51 -0500 Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (windows-nt) Cancel-Lock: sha1:Io0j86b4JwpeiTYaR4wQWNY6tr8= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: abuse@flashnewsgroups.com Organization: FlashNewsgroups.com X-Trace: 4c68b45b816db759e00d415423 Xref: g2news2.google.com comp.lang.ada:8529 Date: 2007-01-24T21:32:51-05:00 List-Id: Maciej Sobczak writes: >> Ah, internationalization of error messages. Again, I think the HTTP >> component itself needs to be internationalized to make that work >> properly, so it is simpler for the HTTP component to put the error >> message string in the exception. > > No. I've been involved in an application for the Belgian market, where > there is more than one official language. It was an application for > the call center, where operators needed a possibility to switch the > display language at *run time*, depending on the preferences of the > client calling them, so that the operator need not be a simultaneous > translator. This means dynamic dictionary switching. Can your HTTP > component do this? I mean - have you *foreseen* an appropriate API for > switching the dictionary between French and Flemish? I guess no. Then you "guess" wrong. Of course you should be able to switch languages at run time; that's an obvious requirement. On the other hand, I've never actually written an internationalized program. Maybe the current tools are not as good as they should be. > Low-level components should *never* be involved in user-interface > tasks like message composition. They should provide *information*, but > not *messages*. Ada got it wrong by focusing on the latter in > exception handling. Well, I guess I don't know enough about internationalization. In my main project at work, it is much easier to format the messages at the level where the relevant information is available. >>> otherwise designers cannot make free paradigm choices. >> In general that is a Good Thing. > > I don't agree. Not in general. By "free paradigm choice" I mean the > choice that is not imposed by implementation constraints. In > particular, the choice between exception and return code should not be > based on their different type-safety abilities. Actually, I was trying to say "free paradigm choice is a good thing". Obviously what I actually wrote can be taken to mean the opposite :(. -- -- Stephe