This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/23065] MAXPATHLEN usage in fortran/{scanner,module}.c


------- Additional Comments From kargl at gcc dot gnu dot org  2005-08-01 16:43 -------
Posix says:

  Pathname Variable Values

  The values in the following list may be constants within an
  implementation or may vary from one pathname to another. For
  example, file systems or directories may have different characteristics.

  A definition of one of the values shall be omitted from the <limits.h>
  header on specific implementations where the corresponding value is equal
  to or greater than the stated minimum, but where the value can vary
  depending on the file to which it is applied. The actual value supported
  for a specific pathname shall be provided by the pathconf() function.

  {PATH_MAX}
    Maximum number of bytes in a pathname, including the terminating
    null character.
    Minimum Acceptable Value: {_POSIX_PATH_MAX}

So, does GNU define _POSIX_PATH_MAX?

Does GNU support pathconf()?

I read the other thread where it is suggested that a non-portable
GNU extension should be used.  The gfortran source is fairly clean
from such kludges, and I would oppose the introduction of one.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23065


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]