June 29, 2005Re: Even if Object.print isn't going to be removed for now, it ought
Posted in reply to Sean Kelly
Sean Kelly wrote: <snip> > I did this a while back in Ares, and I can think of one one reason > for keeping print() in place: it facilitates displaying meaningful > error messages when exceptions are thrown in an out of memory > condition. But were this sufficient reason to keep it, I'd vote for > moving it into Exception and dropping it from Object. Further to the discussion we've just had, even if there is a reason to keep it, there's no reason it should remain in its current form. As I said in my original post: >> The problem is that Object.print gives the application no control over what to output to. Stewart. -- My e-mail is valid but not my primary mailbox. Please keep replies on the 'group where everyone may benefit.