Re: Proposal, Heirarchical module structure for tools

I have a feeling I'm about to get shouted down because Hat is not  
just a debugger... But...

The Debug. namespace already exists, why not Debug.Hat?

Directly in response to Neil - we do need Hat in the structure  
whichever we choose - what if there's another Debugging/Tracing tool  
with an Observe module?

Bob

On 10 Oct 2006, at 16:32, Neil Mitchell wrote:

> Hi
>
>> Yes, it matters a great deal.  We have reserved the 'Hat' top-level
>> namespace for the exclusive use of trace-transformed programs.  No- 
>> one
>> should ever use that namespace intentionally for anything else.
>
> Fair enough, seems reasonable. Although then I wonder if we need the
> "Hat" part, just Tracing.Observe should be enough, since its just as
> unique, and its in the Hat repo so makes it clear enough.
>
>> My suggestion would be just to drop that part.  So, e.g.
>>
>>    Tracing.Hat.Observe
>>    Tracing.Hat.Trail
>>    Tracing.Hat.SExp
>>    Tracing.Hat.HighlightStyle