On Jun 9 10:07, Ken Brown wrote:
> On 6/9/2016 8:32 AM, Corinna Vinschen wrote:
> > Can you please define crypt, encrypt and setkey explicitely in unistd.h
> > per POSIX, rather than including crypt.h? This would not only be target
> > independent, it would also be more correct. As a side effect
On 06/09/2016 08:07 AM, Ken Brown wrote:
> On 6/9/2016 8:32 AM, Corinna Vinschen wrote:
>> Can you please define crypt, encrypt and setkey explicitely in unistd.h
>> per POSIX, rather than including crypt.h? This would not only be target
>> independent, it would also be more correct. As a side ef
On 6/9/2016 8:32 AM, Corinna Vinschen wrote:
Can you please define crypt, encrypt and setkey explicitely in unistd.h
per POSIX, rather than including crypt.h? This would not only be target
independent, it would also be more correct. As a side effect I will
have to come up with a new version of
On Jun 9 08:05, Ken Brown wrote:
> On 6/9/2016 5:00 AM, Corinna Vinschen wrote:
> > Hi Ken,
> >
> > On Jun 8 17:18, Ken Brown wrote:
> > > According to Posix, including should bring in the declaration
> > > of
> > > crypt. The glibc and FreeBSD headers are consistent with this, but
> > > Cyg
On 6/9/2016 5:00 AM, Corinna Vinschen wrote:
Hi Ken,
On Jun 8 17:18, Ken Brown wrote:
According to Posix, including should bring in the declaration of
crypt. The glibc and FreeBSD headers are consistent with this, but Cygwin's
aren't.
$ cat test.c
#include
int
main (void)
{
const char *
Hi Ken,
On Jun 8 17:18, Ken Brown wrote:
> According to Posix, including should bring in the declaration of
> crypt. The glibc and FreeBSD headers are consistent with this, but Cygwin's
> aren't.
>
> $ cat test.c
> #include
>
> int
> main (void)
> {
> const char *key = NULL;
> const char
