php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Doc Bug #61473 The PHP Documentation is missing clear expectations on filesystem separators
Submitted: 2012-03-22 12:38 UTC Modified: 2013-01-26 11:45 UTC
From: daveespionage at gmail dot com Assigned:
Status: Not a bug Package: Documentation problem
PHP Version: Irrelevant OS: Windows 7 64 bit
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: daveespionage at gmail dot com
New email:
PHP Version: OS:

 

 [2012-03-22 12:38 UTC] daveespionage at gmail dot com
Description:
------------
From Bug #61441

[2012-03-20 10:06 UTC] pajoye@php.net
Expected behavior. All files operations working with paths to clean or resolve 
them returns the OS specific directory separator.

[2012-03-20 21:07 UTC] daveespionage at gmail dot com
@pajoye: Is this in the PHP documentation anywhere?  I cannot find it in 
http://php.net/manual/en/function.readlink.php or the parent 
http://www.php.net/manual/en/ref.filesystem.php

Should I file a missing documentation bug?

Thanks!

Expected result:
----------------
Filesystem-related functions or parent Filesystem pages in documentation should 
clearly state what sort of directory separators will be returned (OS-specific, or 
OS-agnostic)



Actual result:
--------------
There is indication of support for Windows for many of the filesystem functions, 
but no clear documentation stating how these functions will return directory 
separators.  

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2013-01-26 11:45 UTC] krakjoe@php.net
As stated, this is expected behaviour.
 [2013-01-26 11:45 UTC] krakjoe@php.net
-Status: Open +Status: Not a bug
 
PHP Copyright © 2001-2026 The PHP Group
All rights reserved.
Last updated: Tue Oct 06 05:00:01 2026 UTC