From: Mike808 <mi...@ne...> - 2000-07-27 02:11:25
|
"Mark A. Hershberger" wrote: > >>>>> "M" == Mike808 <mi...@ne...> writes: > M> Well, it helps when dealing with file paths in particular, > M> since Macs VMS, and Win32 in particular are a bit weird in this > M> regard. > Is <xsl:include href="my:Mac:File"> or <xsl:include > href="my\windows\file"> really valid (see > http://www.ietf.org/rfc/rfc2396.txt)? Or is this not what you are > talking about? I was thinking more like <xsl:include href="file:///DRIVE|/dir/file"> At *some* point XSLT will have to talk to the OS to open this file. Knowing how to construct a filepath is helped with $OS. Read the "Mapping Notes" of URI::file. $OS was a quick and dirty approach, and it came for free in CGI.pm. > I think this is more of a philisophical issue (education > vs. expediency) than a technical one right now, though. At least at > this stage in the game. Yup. I'd sleep better knowing URI::file was doing things vs a hack from CGI.pm. Expediency won this round. Mike. |