> So my question is, how do the rest of you deal with include files and
locating the unit including them?
I don't know what "deal" here refers to, so I can't answer that. I seldom
use include files except when I have to deal with what the compiler/rtl
face: platform dependent implementation of certain API in a platform
independent unit. Sometimes I use it to have multiple classes in the same
unit but I want each class to be in their own (include) file. Condition
compilation is used to have interface and implementation in one file and is
included twice in each respective section in the unit.
I use grep to locate the units including them (the directive is either {$I
or {$INCLUDE, no other possibilites), nothing special or complex.
> And also can this system for including files be better implemented, for
> example by some IDE feature to figure this out for you and displaying the
> "owning" units.
For IDE, it's up to them of course. For instance, Lazarus uses its own
codetools for source navigation, nothing from the compiler, if that's what
you mean. It already indexes identifiers where they reside, it won't be
difficult to index all {$I and {$INCLUDE as well. It's just since include
files may be included by more than one files, the navigation must be altered
somehow.
--
View this message in context:
http://free-pascal-general.1045716.n5.nabble.com/Please-someone-explain-this-to-me-tp5724028p5724039.html
Sent from the Free Pascal - General mailing list archive at Nabble.com.
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
