comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » IDL 8.2.2 released
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: IDL 8.2.2 released [message #83107 is a reply to message #83056] Wed, 06 February 2013 16:00 Go to previous messageGo to previous message
Mark Piper is currently offline  Mark Piper
Messages: 198
Registered: December 2009
Senior Member
On Wednesday, February 6, 2013 2:01:34 PM UTC-7, Louis Giglio wrote:
>
> I'm going to de-lurk after many years to comment on this. I'm not sure how many routines are David's, but what I have noticed is an increasing tendency for IDL releases to co-opt the functionality of a third-party routine that was in use long before the feature was formally added to IDL. Examples include LEGEND and COLORBAR. LEGEND is a particulary good example because F. K. Knight's version has been available for ~18 years before an official (and incompatible) version was added to IDL.
>
> Co-opting the names of existing routines of course creates headaches because of the resulting naming conflicts.
>
> While I suppose it's good that 8.2.2 includes a new BOXPLOT routine, I note that it conflicts with Martin Schultz's version which I've used for 13 years. It would be nice if each new release of IDL didn't clobber another existing routine in the process.

Hi Louis,

This is a tough one, and IDL's blessing/curse of a single namespace is the problem. Because of this, when I started using IDL (and later when I taught IDL), it was drilled into me that if you release a routine into the wild, you should use a namespace identifier to separate it from another user's routine which may have the same name.

I empathize with the problems that we've created in recent releases by tromping on established routines like LEGEND, COLORBAR and now BOXPLOT and TIMESTAMP, and others. However, I assert that since we (VIS) make IDL, we own the primary
namespace. I think this is necessary to continue to move the language forward.

A possible workaround to allow you to call Martin Schultz's version of BOXPLOT would be to compile it in a startup file:

https://groups.google.com/d/msg/comp.lang.idl-pvwave/6ibcyYf UXzA/WJW6eYZLP5YJ

mp
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: netCDF adding variable to an existing file
Next Topic: nearest node of Delauny tesselation

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 16:09:55 PDT 2025

Total time taken to generate the page: 0.00462 seconds