delorie.com/archives/browse.cgi | search |
From: | talisan99 AT aol DOT com (Talisan99) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: compiler can't find "stdio.h" "no such file or directory" |
Lines: | 12 |
NNTP-Posting-Host: | ladder03.news.aol.com |
X-Admin: | news AT aol DOT com |
Date: | 9 Feb 1999 22:32:49 GMT |
Organization: | AOL http://www.aol.com |
References: | <Pine DOT SUN DOT 3 DOT 91 DOT 990209104005 DOT 24101T-100000 AT is> |
Message-ID: | <19990209173249.21265.00000044@ng126.aol.com> |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
On 8 Feb 1999, CryptoZip wrote: > "stdio.h" means that the include is in the current directory that > you are compiling, or in one of the directories you specify on the > command like with the -I option. This is not true. "stdio.h" causes the compiler to look in the current directory, but after that it behaves exactly like <stdio.h>. The only difference is that with <stdio.h> the current directory is not checked at all. My apologies, I was not aware that the preprocessor worked in this manner. :)
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |