On Wed, May 19, 2010 at 6:09 PM, larryclyons <[email protected]> wrote: > Really? I'll have to try it sometime. I've always used something like > the following: > <cfset fileSeparator = createObject("java", > "java.lang.System").getProperty("file.separator") />
Overly complicated. About the only place where you'd 'win' would be in a port to VMS which uses (or used to use?) a rather different file path structure to DOS / *nix :) Even then it would depend on how Java worked on VMS... if it supported / and mapped it to the weird VMS paths, you'd be fine without anything fancy. Fusebox had a bunch of file separator nonsense in it when I took over and I ripped it all out when I built Fusebox 5.0 and to this day Fusebox doesn't do anything O/S-specific in terms of file paths. It converts \ to / on any path the system gives it - to allow for running on Windows - but uses / everywhere when generating file paths. FW/1 does the same. -- Sean A Corfield -- (904) 302-SEAN Railo Technologies, Inc. -- http://getrailo.com/ An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
