[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: using octal codes for special characters
- Subject: Re: using octal codes for special characters
- From: davidf(at)dfanning.com (David Fanning)
- Date: Mon, 21 Dec 1998 19:39:00 -0700
- Newsgroups: comp.lang.idl-pvwave
- Organization: Fanning Software Consulting
- References: <36781244.2AE028C4@amor.met.fu-berlin.de> <MPG.firstname.lastname@example.org> <3678DBE0.FEB03BEC@amor.met.fu-berlin.de> <MPG.email@example.com> <firstname.lastname@example.org>
- Xref: news.doit.wisc.edu comp.lang.idl-pvwave:13209
Craig (Scrooge) Markwardt (email@example.com) writes:
> Soapbox: May I recommend that *nobody* use double-quote octal codes in
> their new IDL programs. They are abominable to look at, can be
> ambiguous, and are confusing. The fact that the second quote never
> appears is particularly insidious.
> The "single-quote" form is not much better, but at least it is
> consistent in the sense that there are two matching quote characters.
> These two expressions perform the same operation:
> a = '355'OB ; SINGLE QUOTE FORM
> a = "355b ; DOUBLE QUOTE FORM
> I believe the first form should always be preferred.
This takes *all* the fun out of adding octal codes to
your programs. I'm *completely* against it. :^)
And a Merry Christmas to you, Sir!
David Fanning, Ph.D.
Fanning Software Consulting
Phone: 970-221-0438 E-Mail: firstname.lastname@example.org
Coyote's Guide to IDL Progamming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155