[...] > thing. If you start off by describing the process > required to do > engineering work on a large and complex product as > "hoops" and > "arguing," then I think you're probably already off > on the wrong foot, > and you're going to have a very tough time of it.
I don't mean to condemn the process; it's reasonably straightforward. Anything could be streamlined some, but it's not bad. Meem sponsored 2006/617 (strnlen()) for me, and he and others were quite helpful, and undoubtedly served to ensure the correctness of the result. Still, I'm more for the research and code than for even reasonable _discussion_ and _process_, if you prefer those words. I wouldn't rule out doing whatever I can, but only the research, coding, and end result are attractive to me; the rest are merely...perhaps unavoidable. If someone else happened to find the procedural and interactive aspects rewarding, I certainly wouldn't be disappointed, let's put it that way. Meanwhile, here's my quick take on functions (man2 or man3*) present in the table of contents (more or less) for POSIX.1-2008 but not appearing in the SXCE snv_129 man pages. This does _not_ include functions that POSIX.1-2008 in some way extends, like the additional open(2) flags that Joerg pointed out. It may list some that are already present, but simply didn't have a separate man page. It also probably does not include some other interface-but-not-functions, like preprocessor constants, macros, external variables. It's more to give some idea of the scope of what's missing, than anything else. If you see something there that is _not_ missing, please let me know. Eventually I think this needs to grow into a full list of what there's some consensus for adding. In fact, I think there probably ought to be a community whose ongoing concern is tracking standards, with specific projects to implement particular standards or reasonable subsets thereof. This is _way_ more than I can deal with, esp. the kernel functions. Even some that could be strictly library code would be way beyond anything I'm confident about attempting. And I am not any kind of leader or organizer whatsoever. Advocacy, structuring collective activities, project management, none of those are things I would willingly attempt. But some of the str* and wcs* functions don't scare me too much (although no way am I going to try to do assembler versions for speed; last assembler I did was Z80, or maybe MC68000, and not much of either, nor recently). This is actually quite a bit more than I expected to find. I can maybe do some small little part of this. Even if I thought I could do more, or were willing to tackle stuff that I'm unfamiliar or very uncomfortable with, there's way too much here for one person in any reasonable amount of time. And I don't have more than a handful of hours a week to give to it, at most. Still, I would think that except insofar as some subset(s) of these may be optional, I would think the rest should be added, preferably sooner rather than later. I would hope some others could get involved. And if multiple people are involved, some coordination will doubtless be needed. Anyway, here's the list: clock_getcpuclockid dprintf duplocale fchmodat fexecve fmemopen freelocale getdelim getline isalnum_l isalpha_l isblank_l iscntrl_l isdigit_l isgraph_l islower_l isprint_l ispunct_l isspace_l isupper_l iswalnum_l iswalpha_l iswblank_l iswcntrl_l iswctype_l iswdigit_l iswgraph_l iswlower_l iswprint_l iswpunct_l iswspace_l iswupper_l iswxdigit_l isxdigit_l linkat mbsnrtowcs mkdirat mkfifoat mknodat newlocale nl_langinfo_l open_memstream open_wmemstream posix_mem_offset posix_trace_attr_destroy posix_trace_attr_getclockres posix_trace_attr_getcreatetime posix_trace_attr_getgenversion posix_trace_attr_getinherited posix_trace_attr_getlogfullpolicy posix_trace_attr_getlogsize posix_trace_attr_getmaxdatasize posix_trace_attr_getmaxsystemeventsize posix_trace_attr_getmaxusereventsize posix_trace_attr_getname posix_trace_attr_getstreamfullpolicy posix_trace_attr_getstreamsize posix_trace_attr_init posix_trace_attr_setinherited posix_trace_attr_setlogfullpolicy posix_trace_attr_setlogsize posix_trace_attr_setmaxdatasize posix_trace_attr_setname posix_trace_attr_setstreamfullpolicy posix_trace_attr_setstreamsize posix_trace_clear posix_trace_close posix_trace_create posix_trace_create_withlog posix_trace_event posix_trace_eventid_equal posix_trace_eventid_get_name posix_trace_eventid_open posix_trace_eventset_add posix_trace_eventset_del posix_trace_eventset_empty posix_trace_eventset_fill posix_trace_eventset_ismember posix_trace_eventtypelist_getnext_id posix_trace_eventtypelist_rewind posix_trace_flush posix_trace_get_attr posix_trace_get_filter posix_trace_get_status posix_trace_getnext_event posix_trace_open posix_trace_rewind posix_trace_set_filter posix_trace_shutdown posix_trace_start posix_trace_stop posix_trace_timedgetnext_event posix_trace_trid_eventid_open posix_trace_trygetnext_event posix_typed_mem_get_info posix_typed_mem_open pthread_getcpuclockid readlinkat stpcpy stpncpy strcasecmp_l strcoll_l strerror_l strfmon_l strftime_l strncasecmp_l strndup strxfrm_l symlinkat tolower_l toupper_l towctrans_l towlower_l towupper_l uselocale vdprintf wcpcpy wcpncpy wcscasecmp wcscasecmp_l wcscoll_l wcsdup wcsncasecmp wcsncasecmp_l wcsnlen wcsnrtombs wcsxfrm_l wctrans_l wctype_l -- This message posted from opensolaris.org _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
