http://bugzilla.spamassassin.org/show_bug.cgi?id=3506
------- Additional Comments From [EMAIL PROTECTED] 2004-07-27 14:02 -------
Subject: Re: Occasionally seeing "PSPAMD" returned by spamd
On Tue, Jul 27, 2004 at 01:03:07PM -0700, [EMAIL PROTECTED] wrote:
> What I found was: There really isn't a good reason to use ssize_t. The
> functions
> that the value ultimately comes from are recv and SSL_read, both of which are
> declared as returning int. ssize_t is not defined on all platforms and is not
That's wrong, at least on Linux and Solaris. recv returns ssize_t:
ssize_t recv(int s, void *buf, size_t len, int flags);
fd_timeout_read can also use read which is ssize_t:
ssize_t read(int fd, void *buf, size_t count);
which is why fd_timeout_read uses ssize_t.
ssl_timeout_read uses SSL_read only, which returns int, as you said.
While the two can be different, on both Linux and Solaris anyway,
ssize_t == int via typedef. My concern is on what platforms (if any)
does ssize_t != int? If the answer is different than "none", we need
to deal with them differently.
Which platforms don't support ssize_t BTW?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
