On Fri, 21 Jan 2022 00:45:56 +0100
Steffen Nurpmeso wrote:
> I found scan-build to generate a lot of false warnings, so much indeed
> that i stopped using it .. in summer 2017.
You, and most others, (no sarcasm at all here) are much better
at C than I will ever be. I am not even at "amateur" le
On Mon, 8 May 2017 00:03:02 +0200
Alexandre Ratchov wrote:
> On Sun, May 07, 2017 at 02:10:03PM -0400, Andre Smagin wrote:
> >
> > >From my limited testing it appears that sio_getcap() fails if audio
> > device does not have identical recording and playback capabilities
>From my limited testing it appears that sio_getcap() fails if audio
device does not have identical recording and playback capabilities
(examples at the end). If that is indeed the case, could it possibly be
mentioned in the man page somewhere? Perhaps something like:
Index: sio_open.3
==
Hello.
After the recent addition of pledge and privilege separation to rdate,
some error messages get truncated, since the pipe message size for the
child is limited to 256. For example:
$ rdate -n pool.ntp.org
rdate: Failed to connect to server: Can't assign requested address
rdate: Failed to co
"
K&R also say for memcpy "copy n characters from ct to s"
POSIX says for mbstowcs:
"No more than n elements shall be modified in the array pointed to by pwcs."
but I personally find the "shall be modified" form somewhat ambiguous.
--
Andre Smagin
Hello.
mbstowcs(3), wcrtomb(3) and wcstombs(3) use a bit awkward wording -
"the first at most", and repeat "array pointed to by blah" from the
previous sentence.
Perhaps something similar to this diff would make them easier to read?
Index: mbstowcs.3
