[DGD] driver / config file

[Johann N. Schmidt]

Hello,

> [...]
> 
> The driver-object itself also needs to be compiled and for that DGD
> needs to know what the standard include file, the include-directories
> and the create function are (quite often you don't use it, but it _is_
> possible to do something useful in there).

indeed. But the driver object follows different rules already, it does not
inherit the auto object e.g.
it would be no matter of much work to write complete paths to all include
statements in the driver object in any lib i guess.

> 
> If you have a look at the driver-functions that DGD already supports
> you'll see that you can do just about all of the above in LPC already
> by adding some extra code in the driver object and the alternate
> create function could be done by some special code in the auto object.
> 

i can emulate force-inheritance, but not inheritance of another or no
auto object. for example i would like the posibility of having objects
that need not inherit auto more than the driver object.

an example would be that the normal auto object blocks all networking
kfuns, and the user object, which is highly security relevant, and thus
protected in most libs does not inherit auto and the security overhead,
but a small own auto object.

another example would be a generalized kernel lib running different
applications at the second layer, which have different requirements
for efuns.

jns
_________________________________________________________________
List config page:  http://list.imaginary.com/mailman/listinfo/dgd