[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: inc and non-compliant long lines redux
From: |
Andy Bradford |
Subject: |
Re: inc and non-compliant long lines redux |
Date: |
21 Nov 2022 19:46:24 -0700 |
Thus said Ken Hornstein on Mon, 21 Nov 2022 21:41:34 -0500:
> netsec_read() is supposed to RETURN the number of bytes read, just
> like read() does (that's why it's return value is prototyped ssize_t).
Aha, that does make more sense. I thought it was odd that it just
returned OK, but didn't think to actually check the documentation in
netsec.h (except to add another variable to the declaration); otherwise
I would have noticed. Let me see if I can rework it to just return the
number of bytes rather than taking another parameter (and the "buffer"
type change).
Thanks,
Andy
- Re: inc and non-compliant long lines redux, (continued)
- Re: inc and non-compliant long lines redux, Andy Bradford, 2022/11/16
- Re: inc and non-compliant long lines redux, Ken Hornstein, 2022/11/16
- Re: inc and non-compliant long lines redux, Andy Bradford, 2022/11/16
- Message not available
- Re: inc and non-compliant long lines redux, Ken Hornstein, 2022/11/16
- Re: inc and non-compliant long lines redux, Ken Hornstein, 2022/11/16
- Re: inc and non-compliant long lines redux, Andy Bradford, 2022/11/21
- Message not available
- Re: inc and non-compliant long lines redux, Ken Hornstein, 2022/11/21
- Re: inc and non-compliant long lines redux,
Andy Bradford <=
- Re: inc and non-compliant long lines redux, Andy Bradford, 2022/11/22
- Re: inc and non-compliant long lines redux, David Levine, 2022/11/27
- Re: inc and non-compliant long lines redux, Andy Bradford, 2022/11/29
Re: inc and non-compliant long lines redux, Andy Bradford, 2022/11/15