Re: organizing deep source trees with child packages

["Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr>]

Le Thu, 13 Oct 2011 01:38:27 +0200, Greg Moncreaff <moncreg@gmail.com> a  
écrit:
> e.g. I would like something like
>
> foo/bar/narf/narf-able.ads
> foo/bar/narf/narf-able.adb
> foo/bar/narf/narf-baker.ads
> foo/bar/narf/narf-baker.adb
> foo/bar/narf/narf-charlie.ads
> foo/bar/narf/narf-charlie.adb
Or even

foo/bar/narf/able.ads
foo/bar/narf/able.adb
foo/bar/narf/baker.ads
foo/bar/narf/baker.adb
foo/bar/narf/charlie.ads
foo/bar/narf/charlie.adb

I opened a similar thread some months ago. This is all about GNAT  
convention, not Ada. For OS with symbolic (not shortcuts, which are not  
the same), you may use two directory hierarchies, one using symbolic links  
to the other (ex foo/bar/narf/able.ads would be a link to  
foo-bar-narf-able.ads). Or alternatively, use a smart outliner or explorer  
in your text editor or IDE, which will interpret GNAT file name convention  
and turn these into a view with nested directories.

I still not solved the case myself, I feel the way using symbolic links  
too much heavy, and the way relying on a smart outliner or browser in an  
editor, not so smart for others, as this depends on a specific tool. On  
the other hand, this is the best solution to me, as people feeling a need  
for it would enjoy it, while people not disturbed by overlong file names  
could go without it.

Or else a specific GNAT branch patched for this single purpose ?


-- 
“Syntactic sugar causes cancer of the semi-colons.”  [Epigrams on  
Programming — Alan J. — P. Yale University]
“Structured Programming supports the law of the excluded muddle.” [Idem]
Java: Write once, Never revisit