home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.edu:1588 comp.lang.fortran:3484
- Path: sparky!uunet!decwrl!deccrl!news.crl.dec.com!pa.dec.com!sousa.ltn.dec.com!gemmax!hobbs
- From: hobbs@gemmax.enet.dec.com (Steve Hobbs)
- Newsgroups: comp.edu,comp.lang.fortran
- Subject: Re: Case Sensitivity (was Re: Small Language Wanted)
- Message-ID: <1719@sousa.ltn.dec.com>
- Date: 9 Sep 92 12:43:22 GMT
- References: <DAVIS.92Aug23010605@pacific.mps.ohio-state.edu> <1992Aug25.034553.2990@linus.mitre.org> <1992Aug25.104211.1@vxdesy.desy.de> <999@engcon.marshall.ltv.com> <1992Sep8.175330.14163@newshost.lanl.gov>
- Sender: newsa@sousa.ltn.dec.com
- Reply-To: hobbs@gemmax.enet.dec.com (Steve Hobbs)
- Followup-To: comp.edu
- Organization: Digital Equipment Corporation
- Lines: 22
-
- In article <1992Sep8.175330.14163@newshost.lanl.gov>, jlg@cochiti.lanl.gov (Jim Giles) writes:
-
- >In the meantime, case *INsensitivity* allows the use of case for
- >emphasis and for documentation. This is also a minor convenience.
- >Which dominates and in what contexts is a subject for research.
- >But, I feel that case sensitivity is best when it has specific
- >meaning to the language (like: all identifiers which begin with
- >uppercase are function or constructor names - and the compiler
- >enforces that).
-
- Reminds me of the original FORTRAN I definition where only variables
- beginning for I,J,K,L,M,N were "fixed point" while all others had to
- be "floating point" with no exceptions. Later, in FORTRAN II they added
- functions. Arithmetic statement functions, the "closed" (library intrinsic),
- and the "open" (built-in intrinsic) functions had to end with the letter "F"
- and were fixed-point only if they began with the letter "X". (What
- consistency, MOD was an integer variable while MODF was a floating function).
-
- In FORTRAN IV they allowed the programmer more freedom with choosing his
- identifier names.
-
-
-