Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!dkuug!dkuugin!keld
From: keld@login.dkuug.dk (Keld J|rn Simonsen)
Newsgroups: comp.std.internat
Subject: Re: Reneging on promises (Internationalization)
Message-ID: <keld.665177880@dkuugin>
Date: 29 Jan 91 19:38:00 GMT
References: <4934@srava.sra.co.jp> <2445@enea.se> <4939@srava.sra.co.jp> <2469@enea.se>
Sender: news@slyrf.dkuug.dk
Lines: 19

sommar@enea.se (Erland Sommarskog) writes:

>Also sprach Erik M. van der Poel (erik@srava.sra.co.jp):
>>codes, and (b) is where you get the software to deal with ISO 646 by
>>avoiding the use of ISO 646 substitutable characters in programming
>>constructs, etc. With (b) you create incompatibility between e.g.
>>Scandinavia and USA, which I would think is a very big disadvantage.

>Only if we hack the compiler locally or write our own stuff. What
>I want is of course alternative characters, so I don't have to
>use the brackets and braces. Some languages like Pascal provides
>this.

Actually this can be done in the current ISO/ANSI C standard also,
via the trigraph sequences. And other proposals have been made
for ISO/ANSI C, because some people (including myself) do not
find the trigraphs very useful (they are unreadable, IMHO).

Keld Simonsen