From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.5-pre1 Date: 21 Oct 92 23:51:27 GMT From: dog.ee.lbl.gov!hellgate.utah.edu!caen!zaphod.mps.ohio-state.edu!rpi!bu.ed u!inmet!spock!stt@ucbvax.Berkeley.EDU (Tucker Taft) Subject: Re: Implementations are allowed (not required) to accept umlauts in co mments in Ada83 Message-ID: <1992Oct21.235127.5983@inmet.camb.inmet.com> List-Id: In article <1992Oct21.171342.14240@wdl.loral.com> mab@wdl39.wdl.loral.com (Mark A Biggar) writes: >Ada 9x is adopting Latin-1 as its official character set, this includes >using all the extra letters in identifiers and any latin-1 characters >at all in comments. Actually, the ISO WG9 (working group on Ada) has now allowed Standard.Character to be Latin-1 rather than ASCII (ISO-646) in Ada 83 compilers. As Mark implies, this will be required for Ada 9X. Furthermore, Ada 9X will have a "Wide_Character" (and Wide_String) in Standard corresponding to the 16-bit Basic Multilingual Plane (BMP) of ISO 10646, otherwise known as Unicode. Any Unicode character is permitted in comments (in fact, any character at all is permitted in comments if you can get your compiler to swallow it, though some characters might reduce portability of the source (or at least its representation)). We are also considering allowing some of the BMP/Unicode characters in identifiers, either for all compilers, or as a localization option. This last part is still somewhat up in the air, given the relatively recent approval of ISO 10646, and the somewhat confliciting concerns of localization and portability. >Mark Biggar >mab@wdl1.wdl.loral.com S. Tucker Taft stt@inmet.com