Bug #843
Missing MAXNAMLEN?
Status:
Closed
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Description
FreeBSD, NetBSD, linux all define MAXNAMLEN in dirent.h, but not DFly.
Is this an oversight or deliberate?
History
#1
Updated by joerg over 9 years ago
Updated by Deliberate. It doesn't make any sense and PATH_MAX or NAME_MAX should be
used instead. MAXNAMLEN is the historic limitation of FFS, for the
archive.
Joerg
#2
Updated by wa1ter over 9 years ago
Updated by Yes, I see now. This is how linux works around it:
# ifdef NAME_MAX
# define MAXNAMLEN NAME_MAX
# else
# define MAXNAMLEN 255
# endif
# endif
#3
Updated by pavalos over 5 years ago
Updated by - Description updated (diff)
- Status changed from New to Closed
- Assignee deleted (
0)