Mail Archives: djgpp-workers/1998/06/01/13:23:12
Somebody complained that MAXDIR, MAXFILE etc constants on dir.h son't
know about long file names. Here's a patch:
*** include/dir.h~0 Fri Apr 26 23:09:18 1996
--- include/dir.h Fri May 29 19:56:38 1998
***************
*** 56,66 ****
#define FA_ARCH 32
/* for fnmerge/fnsplit */
! #define MAXPATH 80
#define MAXDRIVE 3
! #define MAXDIR 66
! #define MAXFILE 9
! #define MAXEXT 5
#define WILDCARDS 0x01
#define EXTENSION 0x02
--- 56,66 ----
#define FA_ARCH 32
/* for fnmerge/fnsplit */
! #define MAXPATH 260
#define MAXDRIVE 3
! #define MAXDIR 256
! #define MAXFILE 256
! #define MAXEXT 255
#define WILDCARDS 0x01
#define EXTENSION 0x02
*** src/libc/dos/dir/fnsplit.t~0 Tue Dec 26 18:47:10 1995
--- src/libc/dos/dir/fnsplit.txh Fri May 29 19:58:40 1998
***************
*** 45,51 ****
@subheading Description
This function decomposes a @var{path} into its components. It is smart
! enough to know that @code{.} and @code{..} are directories.
The @var{drive}, @var{dir}, @var{name} and @var{ext} arguments should
all be passed, but some or even all of them might be @code{NULL} pointers.
Those of them which are non- AT code{NULL} should point to buffers which have
--- 45,53 ----
@subheading Description
This function decomposes a @var{path} into its components. It is smart
! enough to know that @code{.} and @code{..} are directories, and that
! file names with a leading dot, like @file{.emacs}, are not all extensions.
!
The @var{drive}, @var{dir}, @var{name} and @var{ext} arguments should
all be passed, but some or even all of them might be @code{NULL} pointers.
Those of them which are non- AT code{NULL} should point to buffers which have
- Raw text -