John Darrington <[EMAIL PROTECTED]> writes: > I'm not so sure that I entirely agree. Explicitly #including the path > could get cumbersome if several levels of directories are used. For > example, in the structure you suggested, we'd be seeing lines like: > > #include "commands/dictionary/value-labels.h":
I'm not sure that's a big deal. You have to dedicate a full line to each #include in any case. > On the other hand, this does have the advantage that it makes the > programmer think more carefully about what he's depending upon. Right > now, I have mixed opinions about which is the better way. Well, no need to decide right now. Actually, I'd suggest that for doing initial work on reorganization, adding an -I for every directory is the easiest way. That gives you the freedom to move files around without having to adjust any #include's at all. Then later you can fix up the include path and adjust #include's to match. I'm preparing a revised proposal with rationale and will pass it along soon. -- "doe not call up Any that you can not put downe." --H. P. Lovecraft _______________________________________________ pspp-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/pspp-dev
