[DGD]Initializing problem
Erwin Harte
harte at xs4all.nl
Fri Apr 20 17:38:22 CEST 2001
On Fri, Apr 20, 2001 at 10:26:28AM -0500, Jason Cone wrote:
> > -----Original Message-----
> > From: Erwin Harte [mailto:harte at xs4all.nl]
> > Sent: Friday, April 20, 2001 10:04 AM
> > To: dgd at list.imaginary.com
> > Subject: Re: [DGD]Initializing problem
> >
> > Attached you'll find a minimal ~System implementation containing the
> > following files (and one directory):
> >
> > -rw-r--r-- harte/harte 340 2001-04-20 16:51:52 include/System.h
> > [...]
>
>
> Given the following:
>
> include_dirs = ({ "/include", "~/include" }); /* directories to
> search */
>
> in the config file (I assume you're using the same one that's distributed
> with the source), wouldn't it be "more correct" to place the 'System.h' file
> in /usr/System/include rather than /kernel/include?
Not sure. I would probably also include defines in that file that
could be useful for objects in other /usr directories, at which point
I'm not sure which is easier/better to work with, this one:
# include <System.h>
Or this one:
# include "~System/include/System.h"
I think the /include/System.h file should give general pointers into
the /usr/System/ tree, while ~System/include/ would contain include-
files for specific objects' interfaces.
Erwin.
--
Erwin Harte : `Don't mind Erwin, he gets crabby. :)'
harte at xs4all.nl : -- Par Winzell <zell at skotos.net>
List config page: http://list.imaginary.com/mailman/listinfo/dgd
More information about the DGD
mailing list