Actions
Bug #843
closedMissing MAXNAMLEN?
Status:
Closed
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Description
FreeBSD, NetBSD, linux all define MAXNAMLEN in dirent.h, but not DFly.
Is this an oversight or deliberate?
Updated by joerg almost 17 years ago
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
Updated by wa1ter almost 17 years ago
Yes, I see now. This is how linux works around it:
- ifdef NAME_MAX
- define MAXNAMLEN NAME_MAX
- else
- define MAXNAMLEN 255
- endif
- endif
Updated by pavalos over 12 years ago
- Description updated (diff)
- Status changed from New to Closed
- Assignee deleted (
0)
Actions