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/eclipseReceived on Thu May 15 11:51:55 2003
This archive was generated by hypermail 2.1.8 : Wed 16 Nov 2005 06:08:21 PM GMT GMT