tag:blogger.com,1999:blog-1959052963816936322.post231573975146652504..comments2008-11-06T14:16:06.114-08:00Llewellyn Falcohttp://www.blogger.com/profile/11668997629228826023noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-1959052963816936322.post-90949893765813810972008-11-06T14:16:00.000-08:002008-11-06T14:16:00.000-08:00Maybe i didn't get the point, but...<BR/><BR/>1) If you want to see details about your object, you can use the debugger. In good RAD tools, the IDE lets you see the state of each attribute just using things like "Object Inspector".<BR/><BR/>2) If you want to replace a lot of asserts, put them in a separated method that does exactly this. But if you want to check if a object is valid (check its state), add it a method "IsValid":<BR/>game.Add( 5 );<BR/>game.Add( 4 );<BR/>game.Add( 7 );<BR/>game.Add( 2 );<BR/>AssertTrue( game.IsValid() );<BR/><BR/>You can still create a "IValidateMySelf" interface so that your objects can inherit from it to make this job generic:<BR/><BR/>ApproveMe(IValidateMySelf obj)<BR/>{<BR/> AssertTrue( obj.IsValid() );<BR/>}<BR/><BR/>So...<BR/><BR/>game.Add( 5 );<BR/>game.Add( 4 );<BR/>game.Add( 7 );<BR/>game.Add( 2 );<BR/>ApproveMe( game );<BR/><BR/>Isn't easier ?Thiago Delgado Pintohttp://www.blogger.com/profile/00791998615484436526noreply@blogger.com