Re: File-Paths exceeding MAX_PATH on Windows

From: Date: Tue, 08 Jan 2013 05:48:54 +0000
Subject: Re: File-Paths exceeding MAX_PATH on Windows
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to internals+get-64654@lists.php.net to get a copy of this message
hi, On Mon, Jan 7, 2013 at 10:22 PM, Ferenc Kovacs <tyra3l@gmail.com> wrote: > 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.)? All of them, as the paths are passed right to the kernel APIs, without any system checks like in the higher level APIs (posix or win32). >> 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? I mean 6 as the changes are rather big. It could be possible in 5.6 but I rather prefer to target the next major. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org

« previous php.internals (#64654) next »