Re: PL/I string representations

From: robin (robin_v_at_bigpond.mapson.com)
Date: 12/31/03 

Date: Wed, 31 Dec 2003 08:34:11 GMT

Randy Howard <randy.howard@FOOmegapathdslBAR.net> writes:
> In article <f5dda427.0312290803.486d9100@posting.google.com>, spinoza1111
> @yahoo.com says...

> If you think it enhances readability to use variable names that are
> also language keywords, you need to have your head bored for the
>simples.

One of the principal reasons for not reserving keywords
is that any language extension will not affect existing
programs.
It also helps by not having to refer to a long list
of keywords when writing programs, in case one inadvertently
uses an obscure keyword for a variable.

Relevant Pages

  • Re: keyword capitalization -- current practice
    ... for identifiers and all caps for language keywords, with the latter handled automagically by emacs. ... You can access it via the menu under Options>> Customize Emacs>> Browse Customization Groups. ... Then the F90 mode is available under Programming>> Languages>> F90, with the specific setting named F90-Auto-Keyword-Case. ... some earlier versions of the F90-mode elisp file don't pick up all of the F95 keywords. ...
    (comp.lang.fortran)
  • Re: PL/I string representations
    ... >> also language keywords, you need to have your head bored for the ... but I don't think what you wrote differs ... with the statement that it does not enhance program readability. ...
    (comp.programming)
  • Re: The @ symbol
    ... to allow language keywords as names. ... a VB.NET developer could decide that the ... anyone following the .NET naming conventions would ...
    (microsoft.public.dotnet.languages.csharp)