libposix-development Mailing List for libposix (Page 9)
Status: Pre-Alpha
Brought to you by:
hdante
You can subscribe to this list here.
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(16) |
Jun
(122) |
Jul
(49) |
Aug
(19) |
Sep
(6) |
Oct
(4) |
Nov
(1) |
Dec
|
---|
From: Henrique A. <hd...@gm...> - 2009-06-01 02:19:58
|
I want to give full access to the wiki, but I have no idea how to do that. I'll send a message to SF. 2009/5/31 David Rocamora <dr...@gm...>: > Henrique, > > Can you open up the permissions on the wiki so I can create a page > called "function list" or what not. I think we should start with the > list we are describing there and have each function link to another > wiki page if more description is needed. The wiki seems locked down > now so I can't add the page myself. > > Thanks, > Dave > > On Thu, May 28, 2009 at 3:23 PM, Henrique Almeida <hd...@gm...> wrote: >> >> >> 2009/5/28 Tordek <ke...@gm...>: >>> Henrique Almeida wrote: >>>> 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. >>>> >>> >>> Yes, it is. >> >> Nice. >> >>>> 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.). >>> >>> Do we have a wiki, or another place to post this to? A specific >>> format? (writing the full description of a function as an example >>> would be a great start). >>> >>> I'd strongly reccomend a wiki, to make it highly navigable >>> (categorizing functions per difficulty, and implementedness, for one). >> >> Yes, we definitely need a wiki. SF provides MediaWiki. I have activated it >> on: >> >> http://apps.sourceforge.net/mediawiki/libposix/index.php?title=Main_Page >> >> However, at some moment we'll need to provide a clean and uniform (and >> unique) appearance to the whole site, so we'll need to play with the CSS >> stuff in the wiki. Can you do this ? (btw, we'll need to setup a task >> management page too) >> >> At the moment, the table needs the following >> - function name >> - requirement (mandatory or the option group which it belongs) >> - whether it's obsolescent or not >> - expected difficulty >> >> The table will grow later, but let's keep it simple for now. For the >> functions atoi, crypt and dprintf that would be: >> >> atoi mandatory (not obsolescent) easy >> crypt XSI option (not obsolescent) medium >> dprintf mandatory (not obsolescent) hard >> >> There's another wiki available in SF, called Wikispaces, I don't know if it >> would be better than MediaWiki, though, I've looked at their home page and >> it doesn't seem to be any docs there. >> >>> >>> -- >>> Guillermo O. «Tordek» Freschi. Programador, Escritor, Genio Maligno. >>> http://tordek.com.ar :: http://twitter.com/tordek >>> http://www.arcanopedia.com.ar - Juegos de Rol en Argentina >>> >>> >> >> >> >> -- >> Henrique Dante de Almeida >> hd...@gm... >> >> >> ------------------------------------------------------------------------------ >> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT >> is a gathering of tech-side developers & brand creativity professionals. >> Meet >> the minds behind Google Creative Lab, Visual Complexity, Processing, & >> iPhoneDevCamp as they present alongside digital heavyweights like Barbarian >> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com >> _______________________________________________ >> Libposix-development mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libposix-development >> >> > -- Henrique Dante de Almeida hd...@gm... |
From: David R. <dr...@gm...> - 2009-05-31 22:28:08
|
Henrique, Can you open up the permissions on the wiki so I can create a page called "function list" or what not. I think we should start with the list we are describing there and have each function link to another wiki page if more description is needed. The wiki seems locked down now so I can't add the page myself. Thanks, Dave On Thu, May 28, 2009 at 3:23 PM, Henrique Almeida <hd...@gm...> wrote: > > > 2009/5/28 Tordek <ke...@gm...>: >> Henrique Almeida wrote: >>> 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. >>> >> >> Yes, it is. > > Nice. > >>> 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.). >> >> Do we have a wiki, or another place to post this to? A specific >> format? (writing the full description of a function as an example >> would be a great start). >> >> I'd strongly reccomend a wiki, to make it highly navigable >> (categorizing functions per difficulty, and implementedness, for one). > > Yes, we definitely need a wiki. SF provides MediaWiki. I have activated it > on: > > http://apps.sourceforge.net/mediawiki/libposix/index.php?title=Main_Page > > However, at some moment we'll need to provide a clean and uniform (and > unique) appearance to the whole site, so we'll need to play with the CSS > stuff in the wiki. Can you do this ? (btw, we'll need to setup a task > management page too) > > At the moment, the table needs the following > - function name > - requirement (mandatory or the option group which it belongs) > - whether it's obsolescent or not > - expected difficulty > > The table will grow later, but let's keep it simple for now. For the > functions atoi, crypt and dprintf that would be: > > atoi mandatory (not obsolescent) easy > crypt XSI option (not obsolescent) medium > dprintf mandatory (not obsolescent) hard > > There's another wiki available in SF, called Wikispaces, I don't know if it > would be better than MediaWiki, though, I've looked at their home page and > it doesn't seem to be any docs there. > >> >> -- >> Guillermo O. «Tordek» Freschi. Programador, Escritor, Genio Maligno. >> http://tordek.com.ar :: http://twitter.com/tordek >> http://www.arcanopedia.com.ar - Juegos de Rol en Argentina >> >> > > > > -- > Henrique Dante de Almeida > hd...@gm... > > > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity professionals. > Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > |
From: Henrique A. <hd...@gm...> - 2009-05-31 21:47:43
|
2009/5/31 Henrique Almeida <hd...@gm...>: > Hello ! > > The initial code for libposix is available in the source repository. > For downloading, use: > > git clone ssh://hd...@li.../gitroot/libposix Obviously the above line is incorrect. Use: git clone ssh://<yourid>@libposix.git.sourceforge.net/gitroot/libposix > > The announcement message is available at: > > https://sourceforge.net/forum/forum.php?forum_id=960451 > > Everybody should test it in their favorite linux distro. If you don't > have a linux version yet, Ubuntu is the main development enviroment > that we are going to support. Other good options are the top ranked > distros in distrowatch: > > http://distrowatch.com/ > > Report bugs urgently. You may use Tracker for this: > > https://sourceforge.net/tracker/?group_id=261625 > > There are a lot of tasks that must be done to improve that simple > implementation. It's time for us to assign some roles for each person > in the project. > > -- > Henrique Dante de Almeida > hd...@gm... > -- Henrique Dante de Almeida hd...@gm... |
From: Henrique A. <hd...@gm...> - 2009-05-31 21:46:36
|
Hello ! The initial code for libposix is available in the source repository. For downloading, use: git clone ssh://hd...@li.../gitroot/libposix The announcement message is available at: https://sourceforge.net/forum/forum.php?forum_id=960451 Everybody should test it in their favorite linux distro. If you don't have a linux version yet, Ubuntu is the main development enviroment that we are going to support. Other good options are the top ranked distros in distrowatch: http://distrowatch.com/ Report bugs urgently. You may use Tracker for this: https://sourceforge.net/tracker/?group_id=261625 There are a lot of tasks that must be done to improve that simple implementation. It's time for us to assign some roles for each person in the project. -- Henrique Dante de Almeida hd...@gm... |
From: Henrique A. <hd...@gm...> - 2009-05-29 13:27:22
|
2009/5/28 Chris Forbes <ch...@fa...> > OK, have fixed those few tags. > > Will do another chunk later. > > > > Do we have a plan for how we’re going to arrange this code? Testing plan? > Yes. The library will be split in two main parts. The first part of the library consists of functions that can be implemented in standard ISO C. The second part of the library consists of functions that need some special support. The first part is subdivided into the mandatory functions and optional functions. The second part is divided into system dependent functions, compiler dependents functions and functions that require hand-written optimizations. Besides the avobe, which represents our source code, we also have source code that will be available to end users, for example, the "include" directory, with all the header files. We also need a test directory, which will include unit tests for all the functions we implement and also some integration tests too. Finally, we'll need a directory for our build system, which needs to be cross platform. So the basic directory structure is like this: mandatory/ optional/ system/ compiler/ optimized/ include/ tests/ build/ Subdirectories may be created on demand, if the directories become too big. Testing plan: it's still open. I think our best choice is to adopt a test driven development using both real applications and unit tests as test cases. For example, if we use "Hello world" as a starting point, we'll begin developing only functionality to make "Hello world" to correctly output the string. We can evolve from supporting "Hello world" to supporting, say, "ls", then the all the software from GNU coreutils that don't use extensions, etc. > > > Also, an area I’m a bit fuzzy on is the syscall side of the libc. I assume > this would vary somewhat between kernels? > This part goes on the system dependent part of the library (the "system" directory). We have to define an interface that our cross platform code can call. For example, one function of the interface will be "system_write", which writes a string to a file. For each platform we support, there must be an implementation of "system_write". I'm writing a "hello world" version of our library that shows how to make system calls in linux. I hope to post it to the source repository in the weekend. We'll also need a page for our "bookshelf", so that we have documents available to explain such things. I have a post about making system calls under x86 linux at: http://hdante.blogspot.com/2007/02/new-style-system-call-in-linux-x86-ref.html http://hdante.blogspot.com/2007/02/getting-vsyscall-address-from-elf.html I think the full set of system calls in linux are documented in man pages, but I could only find the 2.4 version online. The latest manpages are available at kernel.org. > > > --Chris > > > > *From:* Henrique Almeida [mailto:hd...@gm...] > *Sent:* Friday, 29 May 2009 9:50 a.m. > *To:* Chris Forbes; lib...@li... > *Subject:* Re: Warm-up task > > > > > 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... > -- Henrique Dante de Almeida hd...@gm... |
From: Tordek <ke...@gm...> - 2009-05-29 06:14:07
|
K was 2 functions (kill and killpg), so I took it as "50 functions starting from K"; here are all 2 Ks and all of L. -- Guillermo O. «Tordek» Freschi. Programador, Escritor, Genio Maligno. http://tordek.com.ar :: http://twitter.com/tordek http://www.arcanopedia.com.ar - Juegos de Rol en Argentina |
From: Henrique A. <hd...@gm...> - 2009-05-28 21:58:55
|
They're replying to me. :-/ I've fixed the reply-to address in the mailing list. 2009/5/28 David Rocamora <dr...@gm...> > Something weird seems to be going on with the list. I'm only getting > mails from Henrique and not anyone else. Anyone else seeing this? > > -Dave > > On Thu, May 28, 2009 at 5:50 PM, Henrique Almeida <hd...@gm...> > wrote: > > > > 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... > > > > > ------------------------------------------------------------------------------ > > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > > is a gathering of tech-side developers & brand creativity professionals. > > Meet > > the minds behind Google Creative Lab, Visual Complexity, Processing, & > > iPhoneDevCamp as they present alongside digital heavyweights like > Barbarian > > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > > _______________________________________________ > > Libposix-development mailing list > > Lib...@li... > > https://lists.sourceforge.net/lists/listinfo/libposix-development > > > > > > > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity professionals. > Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > -- Henrique Dante de Almeida hd...@gm... |
From: David R. <dr...@gm...> - 2009-05-28 21:57:21
|
Something weird seems to be going on with the list. I'm only getting mails from Henrique and not anyone else. Anyone else seeing this? -Dave On Thu, May 28, 2009 at 5:50 PM, Henrique Almeida <hd...@gm...> wrote: > > 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... > > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity professionals. > Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > > |
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... |
From: Henrique A. <hd...@gm...> - 2009-05-28 21:36:28
|
2009/5/28 Tordek <ke...@gm...> > Henrique Almeida wrote: > > http://apps.sourceforge.net/mediawiki/libposix/index.php?title=Main_Page > > > > However, at some moment we'll need to provide a clean and uniform (and > > unique) appearance to the whole site, so we'll need to play with the CSS > > stuff in the wiki. Can you do this ? (btw, we'll need to setup a task > > management page too) > > I suck at design, so i'd have to pass on that task... If I had a > design, I can probably make the CSS for it, though. > > > > > atoi mandatory (not obsolescent) easy > > crypt XSI option (not obsolescent) medium > > dprintf mandatory (not obsolescent) hard > > Some tags are obviously optional (EG: XSR says "The functionality > described is optional"); XSI doesn't say so [1]. Why is XSI > optional? Where's it described as so? You're reading the wrong standard. The home page for POSIX 2008 is: http://www.unix.org/2008edition/ In this link, XSI is properly described as an option: http://www.opengroup.org/onlinepubs/9699919799/help/codes.html#XSI All the option groups are described in the unistd.h page: http://www.opengroup.org/onlinepubs/9699919799/basedefs/unistd.h.html Also, there's a chapter that deals with conformance in general: http://www.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap02.html > > > Some pages [2] show several functions in the Name field. I'm > assuming we're only to describe those assigned to us (to avoid > overlap)? ie, from [2] I'd only do lcong, lrand, and so, but not > jrand since it's before K? Yes, the sequence is to avoid overlap. It doesn't really matter which function you choose, but duplicating work is really really bad. So it's better to describe the functions in order. The full function list is in the following link: http://www.opengroup.org/onlinepubs/9699919799/idx/functions.html > > > [1] http://www.opengroup.org/onlinepubs/009695399/help/codes.html#CX > [2] http://www.opengroup.org/onlinepubs/009695399/functions/lcong48.html > > P.S.: Sorry for all the excessive questioning :P. No problem. > > > -- > Guillermo O. «Tordek» Freschi. Programador, Escritor, Genio Maligno. > http://tordek.com.ar :: http://twitter.com/tordek > http://www.arcanopedia.com.ar - Juegos de Rol en Argentina > > -- Henrique Dante de Almeida hd...@gm... |
From: Henrique A. <hd...@gm...> - 2009-05-28 19:24:30
|
2009/5/28 Tordek <ke...@gm...>: > Henrique Almeida wrote: >> 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. >> > > Yes, it is. Nice. >> 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.). > > Do we have a wiki, or another place to post this to? A specific > format? (writing the full description of a function as an example > would be a great start). > > I'd strongly reccomend a wiki, to make it highly navigable > (categorizing functions per difficulty, and implementedness, for one). Yes, we definitely need a wiki. SF provides MediaWiki. I have activated it on: http://apps.sourceforge.net/mediawiki/libposix/index.php?title=Main_Page However, at some moment we'll need to provide a clean and uniform (and unique) appearance to the whole site, so we'll need to play with the CSS stuff in the wiki. Can you do this ? (btw, we'll need to setup a task management page too) At the moment, the table needs the following - function name - requirement (mandatory or the option group which it belongs) - whether it's obsolescent or not - expected difficulty The table will grow later, but let's keep it simple for now. For the functions atoi, crypt and dprintf that would be: atoi mandatory (not obsolescent) easy crypt XSI option (not obsolescent) medium dprintf mandatory (not obsolescent) hard There's another wiki available in SF, called Wikispaces, I don't know if it would be better than MediaWiki, though, I've looked at their home page and it doesn't seem to be any docs there. > > -- > Guillermo O. «Tordek» Freschi. Programador, Escritor, Genio Maligno. > http://tordek.com.ar :: http://twitter.com/tordek > http://www.arcanopedia.com.ar - Juegos de Rol en Argentina > > -- Henrique Dante de Almeida hd...@gm... |
From: Guilherme M. <gui...@gm...> - 2009-05-28 14:50:50
|
Test |
From: Henrique A. <hd...@gm...> - 2009-05-28 14:36:58
|
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... |
From: David R. <dr...@gm...> - 2009-05-28 00:48:47
|
I think it is probably working. :) -Dave On Wed, May 27, 2009 at 5:22 PM, Henrique Almeida <hd...@gm...> wrote: > Test. > > -- > > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity professionals. Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > _______________________________________________ > Libposix-development mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libposix-development > |
From: Henrique A. <hd...@gm...> - 2009-05-27 21:22:55
|
Test. -- |
From: Henrique A. <hd...@gm...> - 2009-05-27 14:37:23
|
Test -- |
From: Andreas K. <akr...@go...> - 2009-05-27 08:21:52
|
Hello everyone, Often enough, the first step is the hardest. Since there is no available libposix code yet, I set up a minimalistic project with a few simple string-related routines and a Makefile that builds static and dynamic versions of the library. It's still far from being useful in any way, but it's a start upon which other people can build and contribute code. You can download the project here: http://synflood.at/tmp/libposix.tar.gz Any feedback is welcome. Regards, Andreas |