|
>Date: Tue, 30 Jan 01 10:54:53 +1100 >From: "Simon Coulter" <shc@flybynight.com.au> > >This raises a question to which I've never been sure of the answer: It is >certainly portable at the source code level since the compiler will sort out >the proper code-point for an apostrophe but is it portable at run time? > >That is, if I compile the program under CCSID 37 but install it on a system >with some other CCSID where the apostrophe occupies a different code-point >will it still work or will the command analyser hiccup? > >I know that using || |< |> and lower-case command strings in CLPs and >QCMDEXC is a really bad practice for NLS reasons but I've never been sure >about literals in HLLs. Simon, good point. I was thinking of portability in terms of completely different operating systems, say AS/400 and Windows (e.g. ILE RPG and VA RPG). For CCSID to CCSID portability, you shouldn't code literals in your source unless they are invariant characters (apostrophe is invariant). Instead, you should put your "literals" in a file and read them in at runtime. Barbara Morris +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.