× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. April 2008

Re: AW: Assistance With Embedded SQL

BirgittaHauser wrote:
I'd not use the hex value x'7D' for quotes, because it may not be
international. Using two single quotes is the better solution.
Actually, this isn't true. Apostrophe is a member of the invariant character set in EBCDIC. That is, every EBCDIC code set has the apostrophe in the same place, x'7D'. In your other message you reference the characters $, # and @ - these are variant characters and are definitely not in the same place in different languages. I dealt with this in BPCS; I ran the project that removed variant characters from all BPCS source code - it was much more difficult than you might imagine!

Anyway, the only time you can get in trouble with x'7D' is when you are dealing with ASCII or Unicode. Apostrophe is definitely not x'7D' there; in fact almost no characters have the same hex value in ASCII and EBCDIC. Interestingly, CR (carriage return) does have the same value, while LF (linefeed) does not.

Joe

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.