Re: LIST "bug": .Remove on an empty list [message #73983 is a reply to message #73981] |
Tue, 14 December 2010 09:19   |
Paul Van Delst[1]
Messages: 1157 Registered: April 2002
|
Senior Member |
|
|
hello,
Paulo Penteado wrote:
> 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.
Yes, the approach I usually take is to put the desired functionality in a subclass, and then use the subclass for
everything. But, as you said, for such a small change .... I'm not sure what the best approach is. Put in a feature
request to ITTVIS? :o)
> 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).
I know I'm taking the other scripting language analogies waaaay too far, but it would neat if IDL had a better mechanism
for sharing user developed code -- like one does with ruby gems (see http://rubygems.org). Or python eggs.
cheers,
paulv
|
|
|