Hello Markus, * On Sat, Jan 16, 2010 at 11:02:32AM +0100 Markus Stehr wrote: > Am Freitag, den 15.01.2010, 22:01 +0100 schrieb Ullrich von Bassewitz: > > Let's call it an unfortunate implementation :-) > > Shouldnt it be that #include "foo.h" is from the current directoy Why tells us that it "should" be this way? In the case for the ISO standard, there is no mentioning of it. The standard does not even know about directories. And: What if foo.h is included because of some -I include-dir directive, and it resides completely elsewhere? Should it still be from the current dir? If yes, that's exactly the way it works ATM for CC65, and this was the complaint. So, people are expecting it differently. > and > #include <bar.h> is from "$COMPILER_DIR/include" (or /usr/include in > gcc's case...)? Why? Note that if implemented as asked for in this thread, this would be true because of the more general rule (include it from the directory where the currently processed file resides). No need for a special rule. > I have learned it that way... Where? Hopefully, not in the "C-Tutorial" on F-64 that does not teach C, but something different that has just some similarity to C? ;) Regards, Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sat Jan 16 13:08:08 2010
This archive was generated by hypermail 2.1.8 : 2010-01-16 13:08:10 CET