drew
/
acadia-newlib
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Make PATH_MAX consistent with MAX_PATH

This commit is contained in:
Keith Marshall 2010-08-17 21:18:21 +00:00
parent adb4e0f3de
commit 0f0a0b7361
2 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
winsup/mingw/ChangeLog
View File

@ -1,3 +1,8 @@
2010-08-17 Keith Marshall <keithmarshall@users.sourceforge.net>
* include/limits.h (PATH_MAX): Make it agree with Microsoft's
semantically identical MAX_PATH; correct value is 260.
2010-07-25 Keith Marshall <keithmarshall@users.sourceforge.net> 2010-07-25 Keith Marshall <keithmarshall@users.sourceforge.net>
Accept that mingwrt headers are not guaranteed to precede GCC's in the Accept that mingwrt headers are not guaranteed to precede GCC's in the

7
winsup/mingw/include/limits.h
View File

@ -25,10 +25,11 @@
* *
* TODO: NAME_MAX and OPEN_MAX are file system limits or not? Are they the * TODO: NAME_MAX and OPEN_MAX are file system limits or not? Are they the
* same as FILENAME_MAX and FOPEN_MAX from stdio.h? * same as FILENAME_MAX and FOPEN_MAX from stdio.h?
* NOTE: Apparently the actual size of PATH_MAX is 260, but a space is * NOTE: PATH_MAX is the POSIX equivalent for Microsoft's MAX_PATH; the two
* required for the NUL. TODO: Test? * are semantically identical, with a limit of 259 characters for the
* path name, plus one for a terminating NUL, for a total of 260.
*/ */
#define PATH_MAX 259 #define PATH_MAX 260
/* /*
* Characteristics of the char data type. * Characteristics of the char data type.