Re: CVS commit: src/sys/kern
In article <20180505211124.gb18...@britannica.bec.de>, Joerg Sonnenberger wrote: >On Sat, May 05, 2018 at 02:24:32AM +, Christos Zoulas wrote: >> In article <20180504224415.ga11...@britannica.bec.de>, >> Joerg Sonnenberger wrote: >> >On Fri, May 04, 2018 at 03:56:59PM -0400, Christos Zoulas wrote: >> >> Module Name: src >> >> Committed By: christos >> >> Date: Fri May 4 19:56:59 UTC 2018 >> >> >> >> Modified Files: >> >> src/sys/kern: uipc_sem.c >> >> >> >> Log Message: >> >> bump the pathname size to NAME_MAX as POSIX wants. >> > >> >Placing NAME_MAX on the stack is not really desirable, is it? >> >I don't think POSIX really requires them to be allowed either, but the >> >spec is a bit unclear... >> >> It's only 512 and the spec says ENAMETOOLONG if >= NAME_MAX or PATH_MAX... > >Sure, but it is calling other functions, so it can sum up. The >conditions for POSIX errors are sufficient conditions, they are not >exhaustive. Ok, I made it allocate.
Re: CVS commit: src/sys/kern
On Sat, May 05, 2018 at 02:24:32AM +, Christos Zoulas wrote: > In article <20180504224415.ga11...@britannica.bec.de>, > Joerg Sonnenberger wrote: > >On Fri, May 04, 2018 at 03:56:59PM -0400, Christos Zoulas wrote: > >> Module Name: src > >> Committed By: christos > >> Date: Fri May 4 19:56:59 UTC 2018 > >> > >> Modified Files: > >>src/sys/kern: uipc_sem.c > >> > >> Log Message: > >> bump the pathname size to NAME_MAX as POSIX wants. > > > >Placing NAME_MAX on the stack is not really desirable, is it? > >I don't think POSIX really requires them to be allowed either, but the > >spec is a bit unclear... > > It's only 512 and the spec says ENAMETOOLONG if >= NAME_MAX or PATH_MAX... Sure, but it is calling other functions, so it can sum up. The conditions for POSIX errors are sufficient conditions, they are not exhaustive. Joerg
Re: Register new acronym in wtf(6) (Re: CVS commit: src/share/misc)
Kamil Rytarowski wrote: > On 05.05.2018 11:47, Geoff Wing wrote: > > VLC = Variable Length Code (or the video player I use) > > VLA = Variable Length Array > > It has been fixed... Should I move this term to acronyms.comp? Variable Length Code sounds like a good candidate for our acronyms db if it's what you meant. BTW, C99 has a concept similar to VLA. It's called Flexible Array Member (FAM). Perhaps worth adding it too. -- Alex signature.asc Description: PGP signature
Re: Register new acronym in wtf(6) (Re: CVS commit: src/share/misc)
On 05.05.2018 11:47, Geoff Wing wrote: > On Friday 2018-05-04 03:01 +1000, Kamil Rytarowski output: > :Module Name: src > :Committed By:kamil > :Date:Thu May 3 17:01:09 UTC 2018 > : > :Modified Files: > : src/share/misc: acronyms > : > :Log Message: > :Register new acronym in wtf(6) > : > :VLCvariable length array > :Noted by > :cvs rdiff -u -r1.266 -r1.267 src/share/misc/acronyms > > VLC = Variable Length Code (or the video player I use) > VLA = Variable Length Array > > Am I missing something? > > Regards, > Geoff > It has been fixed... Should I move this term to acronyms.comp? signature.asc Description: OpenPGP digital signature
Re: Register new acronym in wtf(6) (Re: CVS commit: src/share/misc)
On Friday 2018-05-04 03:01 +1000, Kamil Rytarowski output: :Module Name: src :Committed By: kamil :Date: Thu May 3 17:01:09 UTC 2018 : :Modified Files: : src/share/misc: acronyms : :Log Message: :Register new acronym in wtf(6) : :VLCvariable length array :Noted by :cvs rdiff -u -r1.266 -r1.267 src/share/misc/acronyms VLC = Variable Length Code (or the video player I use) VLA = Variable Length Array Am I missing something? Regards, Geoff
