Subject: Re: lib/libc/net/rcmd.c: solaris compatibility
To: None <email@example.com>
From: Christos Zoulas <firstname.lastname@example.org>
Date: 02/23/2000 11:09:05
On Feb 23, 6:35pm, email@example.com (firstname.lastname@example.org) wrote:
-- Subject: Re: lib/libc/net/rcmd.c: solaris compatibility
| >| again, I'm happy to bring this in. It may be my fault to put
| >| function prototypes that assumes sa_len, for __ivaliduser_sa and
| >| others. I just need to know proper (and easiest) way to deal with
| >| binary backward compatibility...
| >versioning them might be the easiest solution.
| we do not have prototypes for __ivaliduser_sa and friends, since they
| are not really visible as proper API. I can't do API versioning on it.
If you add them, then versioning will work. But where should they go?