Re: [libposix-development] Warm-up task
Status: Pre-Alpha
Brought to you by:
hdante
From: Henrique A. <hd...@gm...> - 2009-05-28 21:50:26
|
Ok, that was FAST. :-D Chris, there are some tags that don't describe options. "OB" just means obsolescent. asctime and asctime_r are obsolescent, but MANDATORY. Also, "CX" just mean "C extension", it's safe to omit that. Please fix the tags. Also, you don't seem to have joined the mailing list, please join, so that I don't need to forward the messages to you. The full option list is available at: http://www.opengroup.org/onlinepubs/9699919799/basedefs/unistd.h.html For anyone that has spare time, you can get more 50 functions to classify. ;-) Just send a note to the list, so that there's no overlap. 2009/5/28 Chris Forbes <ch...@fa...> > Hi All > > There's only 41 functions in the standard starting with A, but here they > are :) > > --Chris > > -----Original Message----- > From: Henrique Almeida [mailto:hd...@gm...] > Sent: Friday, 29 May 2009 2:37 a.m. > To: lib...@li...; Chris Forbes > Subject: Warm-up task > > First of all, I hope the message reaches everyone, I'm not sure if > the mailing list is working well, so please reply to this post if > you've received it. > > We'll start the project with a simple task. During the project we'll > need to mantain the list with the status of each function in the > project (that is, if it has been implemented, tested, etc.). We have a > little more than 1.000 functions to implement. The standard > distinguishes mandatory and optional functions and, for optional > functions, to which option group they belong. Let's start with the > following: classify 50 functions as either mandatory or optional, and, > if optional, take note of which option group the function belongs. > Also, for each function you classify, attribute an expected difficulty > grade (easy, medium, hard) for its implementation. Finally, take note > if the function is classified as obsolescent (tagged as "OB") or not. > > You can see if the function is mandatory or optional by looking at > its prototype. If there's no remark in the prototype, or if there's a > remark that doesn't have an option group tag, it's mandatory. > Mandatory functions may have extra optional functionality in its > description, but they're mandatory anyway. If there's a remark with an > option code in the function prototype, the function is optional and > the tag represents the option group. > > For example, the "atoi" function is mandatory and has an easy > implementation, while the "crypt" is optional, belongs to the XSI > option group and has a medium implementation. "dprintf" has a "CX" tag > which is not optional, so dprintf is mandatory and has a hard > implementation. > > The full function list is on the "System Interfaces" volume of the > standard. > > Chris Forbes, take 50 functions starting with letter A > David Rocamora, take 50 functions starting with letter F > Guillermo Freschi, take 50 functions starting with letter K > Guilherme Mazzela, take 50 functions starting with letter P > I'll take 50 functions starting with letter U. > > -- > Henrique Dante de Almeida > hd...@gm... > -- Henrique Dante de Almeida hd...@gm... |