RE: TTY debugger and the portray mechanism.

It's not that I'm always trying to hide all the internals. Sometimes I'm
portraying the object with all its logical contents, but trying to hide its
implementation details, just as the way the hash table is portrayed. Other
times I am showing enough information to identify the object, e.g. by
displaying its type and string ID, but hiding its other properties. In other
cases I am hiding everything, because the structure has a lot of logical
contents and there's no need to identify it. 

In the absence of any fancy enhancements, changing the default to
show-nothing rather than show all might be useful, though. 

josh

Josh Singer
Software Developer, Parc Technologies Limited
Tel. +44 (0)207 261 4067
josh.singer@parc-technologies.com
http://www.parc-technologies.com

This e-mail message is for the sole use of the intended recipient(s)
-its contents are the property of Parc Technologies Limited (or its
licensors) and are confidential. Please do not copy, review, use
(except for the intended purposes), disclose or distribute the e-mail
or its contents (or allow anyone else to do so) without our prior
permission. Parc Technologies Limited does not guarantee that this
e-mail has not been intercepted and amended nor that it is
virus-free. You should carry out your own virus checks before opening
any attachment.  Any opinions expressed in this e-mail message are
those of the author and not necessarily Parc Technologies Limited.



> -----Original Message-----
> From: Joachim Schimpf [mailto:j.schimpf@icparc.ic.ac.uk]
> Sent: 15 May 2003 11:52
> To: Stefano Novello
> Cc: josh singer; 'eclipse-bugs@icparc.ic.ac.uk'
> Subject: Re: TTY debugger and the portray mechanism.
> 
> 
> Stefano Novello wrote:
> > 
> > Actually the way Josh was using portray, was intended to 
> hide the internals
> > of some large data structures, that he didn't want to be 
> visible when
> > debugging code outside of their home module.
> > 
> > A print depth that depended on whether the functor was a visible
> > struct/predicate/operator, i.e. one that hides data if it 
> is in a structure
> > with an unknown functor, would:
> > 
> > a) Save him from defining a portray macro to hide the data
> > b) Allow him to define portray to show the data better 
> where it was needed
> 
> That's brilliant! Change the default from show-all to show-nothing
> and the problem goes away. I like it. Is it too radical a change?
> 
> -- 
>  Joachim Schimpf              /             phone: +44 20 7594 8187
>  IC-Parc                     /      mailto:J.Schimpf@imperial.ac.uk
>  Imperial College London    /    http://www.icparc.ic.ac.uk/eclipse
>