Re: LIST "bug": .Remove on an empty list [message #73986 is a reply to message #73983] |
Tue, 14 December 2010 08:49   |
penteado
Messages: 866 Registered: February 2018
|
Senior Member Administrator |
|
|
On Dec 14, 2:06 pm, Paul van Delst <paul.vande...@noaa.gov> wrote:
> Philosophically, I'm a "just because you can extend a class doesn't mean you should" type of guy.
> Pragmatically, I'm a "just extend the damn class!" fellow. :o)
Similarly, for such a small change, I might make a derived class for
local use, but would be reluctant to use it in general, stand-alone
routines (as opposed to programs that already comprise many files), as
the benefit of the method would be outweighed by the hassle of
carrying the extra file around.
Which is why I mentioned I intend to put it into the class I started
writing (have not had the time to touch it in weeks) to provide
several missing things - most importantly, the ability to assign to
elements in arrays contained in lists and hashes (http://
groups.google.com/group/comp.lang.idl-pvwave/browse_thread/t hread/
89ad055656bf6798).
|
|
|