[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug #55449] Use FILENAME_MAX in maxfilename.cpp

From: Steffen Nurpmeso
Subject: Re: [bug #55449] Use FILENAME_MAX in maxfilename.cpp
Date: Sat, 12 Jan 2019 14:42:31 +0100
User-agent: s-nail v14.9.11-134-gcc46cfe8

Eli Zaretskii wrote in <address@hidden>:
 |> Date: Sat, 12 Jan 2019 01:23:34 +0100
 |> From: Steffen Nurpmeso <address@hidden>
 |>|For platforms which don't have the Posix pathconf, maxfilename.cpp \
 |>|should try
 |>|harder, and look at (the ANSI-standard) FILENAME_MAX in addition to \
 |>|the other
 |>|varieties.  Right now, it decides that NAME_MAX is 14 on MS-Windows, \
 |>|which of
 |>|course makes no sense.  One adverse effect of this is that temporary file
 |>|names don't get the "groff" prefix, for no good reason.
 |> Let me be plain one time.  The entire stuff that came in for
 |> Windows polluted the code enormously.
 |I think FILENAME_MAX is Standard ANSI C symbol, so it can/should be

NAME_MAX was also ANSI C by Brian W. Kernighan and Dennis M. Ritchie.
ANSI C says

  NAME_MAX 14 /* longest filename-component; system-dependent */

  Filenames are limited to FILENAME_MAX characters.

|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]