Re: Private Child Unit

[Pascal Ledru <Ledru#m#_Pascal@MSMAIL3.HAC.COM>]

Here is a similar case:

I have a package Net_IO providing thick binding to networking functions
(e.g., Socket).
For example:
    function Socket(Af, Socket_Type, Protocol : Integer) return Socket_T
    ( which also raises an exception if necessary)
    This function calls a similar function frim the Winsock library
(thin binding):
    function socket(af, socket_type, protocol: C.Int) ...
    pragma Import(C, socket, "_socket@12");

All the thick binding functions are in the Net_IO package while the thin
binding functions
are in the private child package Net_IO.Winsock.

Ypu could argue that all the functions from the Net_IO.Winsock package
could be in the body
of Net_IO but using a private child package makes things more modular.

Pascal Ledru