Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado
Re: Modular programming in IDL....trouble
hello, Yes, we have been discovering the same problem here at SMA. Especially since we have so many library routines that some may never have been tested by us personally. I have heard of a few solutions. The first is when writing new programs Ifunctions especially) to use a function that Thomas Oettli here at SMA wrote, called 'newproc', it checks your requested new function name agains all already existing function names (but not yet the routine names that come with the system). If you are interested in this routine I can post it, or put it on our ftp site. The other idea is to add a bogus keyword to your functions. Maybe just the keyword Function. Always put it in the calling of the function, but the function doesn't have to use it. This isn't to bad, but going back to all the old functions and adding this would not be fun. I too would be interested in hering other ideas on this subject. Things like discovering your library has a function named X in it, that compeats with my array X is not a nice thing to discover! -stephen Strebel -- Stephen C Strebel / SKI TO DIE stl@maz.sma.ch / and Swiss Meteorological Institute, Zuerich / LIVE TO TELL ABOUT IT 01 256 93 85 / (and pray for snow)