Mantis Bugtracker

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0006623 [Squeak] Kernel major N/A 08-13-07 06:24 08-13-07 06:24
Reporter wiz View Status public  
Assigned To
Priority low Resolution open  
Status new   Product Version
Summary 0006623: Is there any reason why Object.>>printOn: does not include the object hash.
Description When exploring an object it is extremely useful to know Right Away if objects it contain are the same or different.

Morphs add the object hash as an annotation to their print out.

But some of the object they contain are indistinguishable.

E.G I had a problem where I needed to distinguish between two Gradient fills but the printout were the same.

Rather than patch the problem piecemeal, it would be nice to use the inheritance of object to solve this once and for all. (mostly anyway ).
Additional Information So is there any reason why hash annotation should not be default on printout?
Attached Files

- Relationships

There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
08-13-07 06:24 wiz New Issue

Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
27 total queries executed.
24 unique queries executed.
Powered by Mantis Bugtracker