Nicolas Cellier wrote: > > Sure, object databases are more interesting applications, since you > generally make such mistake only once. > As a beginner, I put a halt in the method once identified as the > source of the problem, and did not understand my mistake at first shot > since it started working again (being recompiled). The good thing is > that it helped me learning some Smalltalk superpowers faster :).
Yes, I love the way that you can come to understand Smalltalk through debugging it. Modification tracking is good for more than just object databases. Object-relational mapping, distributed object systems, debugging, analysis, probably more -- all benefit from being able to tell when an object is modified, and all care at a different level of abstraction from the application itself, so it's better if you don't have to put the modification-detection code in the application code. Regards, -Martin _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
