Related articles |
---|
[4 earlier articles] |
Re: Spell checking identifiers 937-053-0959@kylheku.com (Kaz Kylheku) (2020-06-24) |
Re: Spell checking identifiers tkoenig@netcologne.de (Thomas Koenig) (2020-06-24) |
Re: Spell checking identifiers gautier_niouzes@hotmail.com (2020-06-24) |
Re: Spell checking identifiers gah4@u.washington.edu (2020-06-24) |
Re: Spell checking identifiers johann@myrkraverk.invalid (Johann 'Myrkraverk' Oskarsson) (2020-06-25) |
Re: Spell checking identifiers johann@myrkraverk.invalid (Johann 'Myrkraverk' Oskarsson) (2020-06-25) |
Re: Spell checking identifiers acolvin@efunct.com (mac) (2020-07-09) |
Re: Spell checking identifiers tkoenig@netcologne.de (Thomas Koenig) (2020-07-10) |
Re: Spell checking identifiers gah4@u.washington.edu (2020-07-10) |
From: | mac <acolvin@efunct.com> |
Newsgroups: | comp.compilers |
Date: | Thu, 9 Jul 2020 16:07:45 -0000 (UTC) |
Organization: | A noiseless patient Spider |
References: | 20-06-010 20-06-013 20-06-017 |
Injection-Info: | gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="30668"; mail-complaints-to="abuse@iecc.com" |
Keywords: | errors, history |
Posted-Date: | 09 Jul 2020 13:12:13 EDT |
> You might not want J1 and J_one in the same program.
Similarly, some ancient compiler (Euclid?) had case-insensitive lookup, but
required the same capitalization everywhere
This was much more important in the days of batch systems, where compilers
tried to "correct" your code, because it would be a day before you got
another chance. And because student programs couldn't do any damage.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.