On Tue, Aug 4, 2015 at 4:39 PM, Ferenc Kovacs <tyr...@gmail.com> wrote:
> On Tue, Aug 4, 2015 at 2:22 PM, Nicolas Grekas < > nicolas.grekas+...@gmail.com > > wrote: > > > Hello, > > > > I reported this bug one year ago (https://bugs.php.net/67220) and it is > > now > > closed as "not a bug". I'd like this to be reconsidered. > > > > The documentation of realpath() says: > > > > > realpath() expands all symbolic links and resolves references to > '/./', > > > '/../' and extra '/' characters in the input path ***and returns the > > > canonicalized absolute pathname***. > > > > > > > the last part of this description is IMO what qualifies this behavior on > > MacOSX as a bug. > > > > I'm asking for this now because I spend many hours on Syfony trying to > find > > an efficient workaround, and this is far from easy. Here is the fastest > we > > found (it's a mix of scandir()+getcwd()+caching): > > https://github.com/symfony/symfony/pull/15443 > > > > If realpath were behaving on OSX the same as it does on Windows (and > > Linux), > > I could remove 60 lines of wtf lines. > > > > Do anyone else agree? > > > > Regards, > > Nicolas > > > > I do and commented on the ticket last year. > I just re-opened the issue. So the solution is weither we find a patch for the OSx case , or we patch the documentation to reflect the actual behavior. I confirm that patching realpath() can be tricky, as it expands to thousands lines of code, but nothing is impossible. For myself, I'm not OSx user, nor OSx fan, nor OSx developer, so I can't myself do it, as I dont master that platform and don't care about related bugs. Julien.Pauli
