From: Emiliano Date: 2001-10-24T06:11:49+09:00 Subject: [ruby-talk:23095] Re: Bruce Eckel's opinion of Ruby On Tuesday 23 October 2001 22:43, you wrote: > While nice in its context, this does not work for many paradigms. For > (hypothetical) example, I have a class which maintains some state > information in a database. When an instance is destroyed, I want the > corresponding state deleted out of the database. But I don't know > beforehand when an instance is going to be destroyed, because I am one > programmer on a team of 50 programmers working on this product. It is clear > that a destructor is the most useful way of handling this situation. No offence but I think that a good design up front would be the most useful way of handling this situation. Emile