Dmitry Stogov wrote:
:(
Any ideas how to support this?
Dmitry.
Stefan Walk wrote:
On Monday 24 March 2008 20:28:49 Stanislav Malyshev wrote:
Beats me, I'm sure posix-based systems don't, but it is called "Uniform
Naming Convention" so it's possible somebody might implement it
The fact that it's called "uniform" doesn't mean it works in anything
but Windows :) In UNIX IIRC if one needs to access SMB volume the
regular smb:// URLs are used, or tool-specific syntax. If you have
something like automount, then you have regular /-based URLs, but never
headr of // having any special meaning different from just /.
a) // is valid for windows too
b) cygwin uses //
Regards,
Stefan
It is supported, have you tried it?
Basically, the only way you could subvert this is if you have a relative
path in your include_path, which would never work anyways, as
include_path would change for every single file executed. To be clear,
if there are any slashes in the path, the // will *not* be detected as a
stream wrapper. Here is an example:
oops.broken://UNC/path
The code will detect this as a stream wrapper "oops.broken", but this
example:
/working.example://UNC/path
will correctly detect "/working.example" and "//UNC/path" as 2 separate
paths.
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
