Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado
I was wondering if anyone has experienced any strangeness using IDL for Windows along the lines of long filenames. I find myself in the position of sharing programs with folks who work on UNIX workstations and so they name their program files without regard to the 8.3 standard that PC's had to deal with. Since I'm using IDL under WinNT3.51 and Win95 I assumed that I would have the same kind of flexibility as my UNIX counterparts however I have noticed that if a routine (which can have any length name) resides in a *file* with a non-8.3 form IDL cannot find it. I was wondering if there are any work-arounds short of having to rename *every* file I get from elsewhere to an 8.3 form. Also I've noticed that I cannot OPENW a file that doesn't have an 8.3 form. The only way to do it is to assign the filename I want to use to a string variable and then OPENW using the variable as the file name parameter. Although this is not a critical flaw, it *is* annoying. Does anyone know of any patches/updates to 4.0.1 for WinNT/Win95 that will give IDL the full long filename capability? -- David R. Klassen Department of Physics and Astronomy University of Wyoming Box 3905 University Station Laramie WY 82071 http://faraday.uwyo.edu/grads/dklassen/ drk@uwyo.edu
David R. Klassen wrote: > > I was wondering if anyone has experienced any strangeness using IDL > for Windows along the lines of long filenames. > stuff deleted. Boy, I sure hope that Mr. Stern and the folks that write all those impressive adds that taut IDL's inter-operability on various operating systems notices David's post. It is appaling that such essential features are still uncorrected in V4. -- Mirko Vukovic, Ph.D 3075 Hansen Way M/S K-109 Varian Associates Palo Alto, CA, 94304 415/424-4969 mirko.vukovic@varian.grc.com