Re: Proposal, Heirarchical module structure for tools

Hi,

> > Hat.Lib - directory for libraries, which export a nice API for using
> > in the tools - for example HatCover as Hat.Lib.Cover.
> >
> > Hat.Tool - directory for the tools, for example HatCoverText, as
> > Hat.Tool.Cover
>
> I don't like this division much.  How should I decide whether I'm
> looking for a Lib or a Tool, or a Common?  In principle, everything can
> be treated more or less as a library.  Lib/Tool/Common is a
> meta-category, not a name chosen to reflect the underlying
> functionality.

So where would the library half of HatCover vs the program half of HatCover go?

Thanks

Neil

PS. Debug.Trace is already a module, perhaps we could put things under that ;)