comp.lang.idl-pvwave archive: archive » file

Home » Public Forums » archive » file_basename(): bug or feature?

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

file_basename(): bug or feature? [message #42773]

Thu, 24 February 2005 13:06

Benjamin Hornberger is currently offline

Benjamin Hornberger
Messages: 258
Registered: March 2004

Senior Member

On Unix machines, IDL's file_basename() function doesn't split a path in
Windows format (with backslashes). On Windows machines, it splits both
(yes, I know, on Windows you can also use both to specify a path). Is
this a bug or a feature?

Linux:

IDL> filename='d:\path\to\file.ex
IDL> print,file_basename(filename)
d:\path\to\file.ex
IDL> filename='d:/path/to/file.ex'
IDL> print,file_basename(filename)
file.ex

Windows:

IDL> filename='d:\path\to\file.ex'
IDL> print,file_basename(filename)
file.ex
IDL> filename='d:/path/to/file.ex'
IDL> print,file_basename(filename)
file.ex

I have a situation where a Linux machine has to handle Windows paths,
where this is quite annoying ...

Any comments? Thanks
Benjamin

Report message to a moderator

[Message index]

file_basename(): bug or feature?

By: Benjamin Hornberger on Thu, 24 February 2005 13:06

Previous Topic:	Help optimizing the nested for loops
Next Topic:	Re: file_basename(): bug or feature?

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 10:30:21 PDT 2025

Total time taken to generate the page: 0.56139 seconds