Re: Remaining Interfaces
Enclosed is a markup for these in SUSV2. I'd suggest all the
ones marked SUSV2 be considered with the exception of
those marked removed in SUSV3.
On Feb 28, 5:15pm in "Remaining Interfaces", Stuart Anderson wrote:
>
> All,
> We scrubbed a lot of lingering interfaces at the meeting
> this week. Attached is a short list of the remaining interfaces that
> need to be cleaned up. I see a fgew that I think I know what to do about,
> but I need everyone else to looks over this list, and let me know what
> the disposition of the interface should be. (Included or Excluded), and
> what the reference Specification should be.
>
> asprintf
> closelog SUSV2
> dprintf
> drem
> encrypt SUSV2
> _errno
> fstat SUSV2
> fts_children
> fts_close
> fts_open
> fts_read
> fts_set
> ftw SUSV2
> getchar_unlocked SUSV2 (POSIX.1c)
> getc_unlocked SUSV2 (POSIX.1c)
> getlogin SUSV2
> gettimeofday SUSV2
> glob SUSV2
> glob64
> globfree SUSV2
> globfree64
> glob_pattern_p
> htonl SUSV2
> htons SUSV2
> ilogbf SUSV3 /c99
> ilogbl SUSV3 /c99
> inet_addr SUSV2
> inet_aton
> inet_lnaof SUSV2 (removed in SUSV3)
> inet_makeaddr SUSV2 (removed in SUSv3)
> inet_netof SUSV2 (removed in SUSV3)
> inet_network SUSV2 (removed in SUSV3)
> inet_ntoa SUSV2
> ioperm
> iopl
> j0f
> j0l
> j1f
> j1l
> jnf
> jnl
> lockf SUSV2
> _longjmp SUSV2
> madvise (probably a relation to posix_madvise based
on the draft before the posix_ prefix was added)
> mknod SUSV2
> ntohl SUSV2
> ntohs SUSV2
> scandir
> scandir64
> _setjmp SUSV2
> ssignal
> sysconf SUSV2
> _sys_errlist
> tmpfile SUSV2
> tmpnam SUSV2
> tmpnam_r
> ttyname SUSV2
> ttyname_r SUSV2 (POSIX.1c)
> uncompress
> vasprintf
> vdprintf
> zlibVersion
>
regards
Andrew
Reply to: