Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: [Solved] Need some help getting to my feet Date: Thu, 26 Apr 2018 07:33:08 -0700 Organization: None to speak of Lines: 37 Message-ID: References: <87o9i7ovsc.fsf@bsb.me.uk> <752bbd42-4649-4537-bb9a-01ecc72d3b0c@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="751013466cf4d83a736ec69fbb9af6e9"; logging-data="23088"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18g/Ll11CZKCrNXUPFdX3HT" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:X27/mL/BoAcnQ9cMS2Mc1pKOlyk= sha1:xnC+ZbJLGfNc65ylFZkD/FY/MZI= Xref: csiph.com comp.lang.c:129791 Malcolm McLean writes: [...] > He's also the author of "Teach yourself C" > > Here's an example > > The most commonly required header file is called STDIO.H. Here is the > directive that includes this file > > #include > > You can specify the filename in either upper- or lowercase but lowercase > is the traditional method. The STDIO.H header file contains, among > other things, the information related to the printf() library function. > Notice that the #include directive does not end with a semicolon. > The reason for this is that #include is not a C keyword that can > define a statement. Instead it is an instruction to the C compiler itself. He is of course wrong about standard header names being case-insensitive. Using uppercase might happen to work under Windows, or under some other system with a case-insensitive filesystem, but it's non-standard. Even on Windows, a compiler *could* reject the uppercase form. Mentioning the possibility of using uppercase introduced needless complication for no good reason. And the fact that a #include directive has no semicolon has nothing in particular to do with the fact that it's "an instruction to the C compiler itself". That just happens to be the syntax, which just as easily *could* have required a semicolon. Sloppy reasoning. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"