Re: Project files ads/adb organization

["Randy Brukardt" <randy@rrsoftware.com>]

"Alejandro R. Mosteo" <alejandro@mosteo.com> wrote in message 
news:o2u9tf$9j0$1@dont-email.me...
> I'm overthinking how to organize a library source and have come to this 
> idea (Gnat-specific due to ads/adb files):
>
> - An /spec/ folder with ads files exposing the client interface.
> - An /priv/ folder with ads files for support packages, not intended for 
> direct client use.
> - A /body/ folder for all the bodies.
>
> A variant could be to separate public spec from bodies, but keep private 
> parts together.
>
> I wonder if the idea of separating specs from their bodies could be seen 
> as a poor choice. Certainly it requires developers to use an Ada-aware 
> editor like GPS, but for clients seems appropriate not to mix things they 
> don't need to see.
>
> Opinions? Or "whatever floats your boat?"

I don't think its necessarily "overthinking". For the Janus/Ada runtime, we 
only provide the specifications in the non-embedded packages (don't support 
recompiling the runtime for those). Usually, that's all you need.

For Claw, we just provided it in one bunch, but there aren't very many 
private packages, so almost every .ads is a public specification.

I'd suggest not making it too complicated, but  some sort of separation of 
"public" stuff that clients are supposed to use, and the rest of it, seems 
reasonable.

                          Randy.