Deutsch English Français Italiano |
<ussm67$108sl$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Nick Bowler <nbowler@draconx.ca> Newsgroups: comp.lang.c Subject: Re: Word For Today: =?UTF-8?B?4oCcVWdsaWZpY2F0aW9u4oCd?= Date: Wed, 13 Mar 2024 17:01:59 -0000 (UTC) Organization: A noiseless patient Spider Lines: 19 Message-ID: <ussm67$108sl$1@dont-email.me> References: <uso6or$3t3jn$3@dont-email.me> <usopec$4eob$1@dont-email.me> <usort1$4t2r$1@dont-email.me> <20240312003531.349@kylheku.com> <wwvwmq7x4ex.fsf@LkoBDZeT.terraraq.uk> <usp9m5$7it7$1@dont-email.me> <20240312174600.5b88613545da9f667e06a4c6@g{oogle}mail.com> <uspqa4$bfao$1@dont-email.me> <20240312180904.ac3a5856df424c396689db3e@g{oogle}mail.com> <uspt5n$c2bg$1@dont-email.me> <20240312114213.182@kylheku.com> <usql0p$hk2k$1@dont-email.me> <878r2n839m.fsf@nosuchdomain.example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Wed, 13 Mar 2024 17:01:59 -0000 (UTC) Injection-Info: dont-email.me; posting-host="df5c950dcff23d9b38a753c088ff3b74"; logging-data="1057685"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+TGgiG+fBLCqNI6B6Hbw/5" User-Agent: Pan/0.149 (Bellevue; 4c157ba git@gitlab.gnome.org:GNOME/pan.git) Cancel-Lock: sha1:/ljWRQKvzYZg6K2p6oqPAMMBwg4= Bytes: 2440 On Tue, 12 Mar 2024 16:00:05 -0700, Keith Thompson wrote: > (The standard does mention the possibility that the "foo.h" search is > not supported. Any such implementation would not be able to handle > user-defined header files; perhaps they would have to be installed as > "headers" somehow. In every implementation I know about, the compiler > will *at least* find the foo.h file if it's in the same directory as > the file that includes it. The POSIX-standard compiler commands (c89, c99) require #include searches to work this way so it's not surprising that today, most compilers work like this. However some traditional compilers (for example, VAX C) search relative to the current working directory of the running compiler for #include "foo.h", rather than the directory containing the source file. Standard C does not forbid such behaviour and standard C predates the first version of POSIX.2 by a few years so there are probably some standard C compilers that work like VAX C.