committed: merge with libada-branch

[Laurent GUERBY]

On Tue, 2004-02-10 at 22:15, Zack Weinberg wrote:
> My concern is for people (such as myself) who are *not* familiar with
> Ada.  I have occasion to look in there maybe once a month and every
> time I have to work out from first principles how the krunching scheme
> works.

If you know the Ada package name (from textbook and no IDE around), the
gnatkr tool will give you the crunched name:

$ gnatkr ada.text_io
a-textio

If you're in a file, the package name is at the top and end of the file.

> As for organization of OS specific stuff, the only real suggestion I
> have is that the file names have some obvious relation to the system
> they're intended for, rather than being arbitrary codes.  Directory
> partitioning was just the first thing that came to mind.

For now the table is in ada/Makefile.in, it's not simple
to classify the OS/file correspondance, sometimes
one file is used for half of the OSes, sometimes only
for one OS, so it will not be simple to come with a set
of meaningful prefixes.  

It would be interesting to have more information about
the things that costed you time to come up with concrete solutions.

I use search for filename or search for target
with a text editor in ada/Makefile.in when I'm looking for something.
But if you have a problem involving tasking (where the codes are
used), finding the file is 0.0001% of the problem, the complement
will be understanding interaction between OS threads and up to Ada
tasking constructs.

> > It looks like most of the existing ada/Makefile.in is related
> > to the specifics building the library and tools and we should be able
> > to move that to libada, orthogonal to renaming I'd say.
> 
> Yes, I agree this should be possible.

Will see if it's on Arnaud's plan.

Laurent