Path: csiph.com!xmission!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: Thomas Koenig Newsgroups: comp.compilers Subject: Re: Spell checking identifiers Date: Fri, 10 Jul 2020 07:12:27 -0000 (UTC) Organization: news.netcologne.de Lines: 15 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <20-07-003@comp.compilers> References: <20-06-010@comp.compilers> <20-06-013@comp.compilers> <20-06-017@comp.compilers> <20-07-002@comp.compilers> Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="59714"; mail-complaints-to="abuse@iecc.com" Keywords: lex, history, C, Fortran Posted-Date: 10 Jul 2020 11:23:35 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:2549 mac schrieb: >> 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 Fortran has a a bit of a similar issue with its C interoperability feature. Entities with C binding have global identifiers in Fortran. Fortran is a case-insensitive laguage, so FooBar and foobar look the same to Fortran, and you can not have a C binding to both (but either one would work). In practice, this should not be a big problem.