Re: getline & getline_safe

[Paul Edwards]

"Derek Robert Price" <derek@ximbiot.com> wrote in message 
news:mailman.453.1059059441.8231.bug-cvs@gnu.org...
> Paul Edwards wrote:
>
> >"Derek Robert Price" <derek@ximbiot.com> wrote in message 
> >news:mailman.447.1059051115.8231.bug-cvs@gnu.org...
> >
> >
> >> I don't think you're going to find many PATH_MAX's under 256. I think
> >> UNIX and Windows both have PATH_MAXs of 4096?
> >
> >CVS runs under DOS too.  MVS is/was restricted to 44/52.
>
> What is 44/52?  Why the slash?

Well, filenames are considered to be 44 characters long in any
documentation, and I've seen FILENAME_MAX defined that
way before.

But I also pointed out to a C vendor that you can specify quotes
around the filename, plus you can have a member of a PDS,
which involves using brackets, so that brings it to 2 + 44 + 8 + 2 + 1 = 57.

(not 52 as I erroneously said, just adding 8 for the member).

> >I agree that CVSROOT should be PATH_MAX, or actually, I
> >think it should be FILENAME_MAX,
> >
>
> PATH_MAX is defined to be the maximum length of any path, including the
> filename, I believe, though please point me to the correct reference if
> I am wrong.

PATH_MAX is a Posix extension.  ISO/IEC 9899:1990
provides FILENAME_MAX.

> > but the other strings are
> >not logically related to filenames and thus should be separately
> >defined.  Maybe I wouldn't be so anal to create a USERID_MAX,
> >WHATEVER_MAX, but I would separate filenames that aren't
> >actually stored in the ",v" file to strings that are.  I see those as
> >very different things.
>
> What are you talking about here?  What filenames stored in ,v files?

Filenames AREN'T stored in the repository (,v) files!  Other
strings are.

BFN.  Paul.