> > > It would be indeed nice if the "\\?\" prefix was not needed in userspace > > and php would do the work. But just for now I really would like to see > php > > support for long paths on windows at all. To my mind the changes needed > for > > the prefix workaround are function is minimal-invasive. Correct me, if > I'm > > wrong :) > > I would not ever expose that prefix to userland, the consequences and > how we have to manage it are way too complicated for a user land > scripting languages (even in C apps it is not recommended). >
is this about allowing the user to shot him/herself in the foot, or adding this feature could potentially break some existing functionality (eg. new trick to bypass open_basedir, etc.)? > > A better solution I work on for previous php version (incl. 5.5 as I > won't make it in time) is an extension which would override existing > functions. Next major version (6) will support unicode filenames, > which will solve the 255 chars horrible limitation. > by 6.0 you mean php next after 5.5, or adding this to the core would require a major version for some reason? -- Ferenc Kovács @Tyr43l - http://tyrael.hu
