Paul Eggert wrote: > > If encrypt() is going away, maybe crypt() is going away as well? > > Apparently not. It's not listed as obsolescent on page 3698 line 127090 > of draft 3.
OK. That's consistent with what glibc did in version 2.28. It's really a different facility than encrypt(). Bruno
