libposix-development

[libposix-development] My personal development branch

[Andreas K. <akr...@go...>]

Hello everybody,

As the "broken" branch didn't work out as expected, I found a better way
that both satisfies me in its abilities and also allows other developers to
easily see and merge my changes. I have a fork of libposix uploaded on
GitHub: http://github.com/akrennmair/libposix/tree/master
In this fork, I will regularly keep track of changes in the official
libposix git repository. But it's also simple to merge my commits into the
official libposix repository by executing
git pull git://github.com/akrennmair/libposix.git master
in a clone of the official libposix git repository. Anyway, GitHub is the
place to see and track my changes. Of course, this shall NOT be interpreted
as a way to get independent from the official project, it is merely a way
that helps me work in a more flexible fashion on the things that I want to
work on, plus it makes my changes more visible and also easier to
reintegrate with the official development line.

Nevertheless, I will continue posting short notifications about the things I
currently work on to keep everyone informed. So far, I've worked on some
simple functions including unit tests, and I hope to present a simple
implementation of malloc(), free(), realloc() and calloc() within a day or
two.

Regards,
Andreas

Re: [libposix-development] My personal development branch

[Henrique A. <hd...@gm...>]

 Ok, good idea, git branches rock !

2009/6/5 Andreas Krennmair <akr...@go...>

> Hello everybody,
>
> As the "broken" branch didn't work out as expected, I found a better way
> that both satisfies me in its abilities and also allows other developers to
> easily see and merge my changes. I have a fork of libposix uploaded on
> GitHub: http://github.com/akrennmair/libposix/tree/master
> In this fork, I will regularly keep track of changes in the official
> libposix git repository. But it's also simple to merge my commits into the
> official libposix repository by executing
> git pull git://github.com/akrennmair/libposix.git master
> in a clone of the official libposix git repository. Anyway, GitHub is the
> place to see and track my changes. Of course, this shall NOT be interpreted
> as a way to get independent from the official project, it is merely a way
> that helps me work in a more flexible fashion on the things that I want to
> work on, plus it makes my changes more visible and also easier to
> reintegrate with the official development line.
>
> Nevertheless, I will continue posting short notifications about the things
> I currently work on to keep everyone informed. So far, I've worked on some
> simple functions including unit tests, and I hope to present a simple
> implementation of malloc(), free(), realloc() and calloc() within a day or
> two.
>
> Regards,
> Andreas
>
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>
>


-- 
Henrique Dante de Almeida
hd...@gm...

Re: [libposix-development] My personal development branch

[Henrique A. <hd...@gm...>]

 With git pull, I'm not being able to merge each commit individually in my
branch:

 commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
Merge: 1faac1a... 05b56ea...
Author: Henrique <hd...@us...>
Date:   Sat Jun 6 17:29:37 2009 -0300

    Merge git://github.com/akrennmair/libposix into andreas

    * git://github.com/akrennmair/libposix:
      implemented abs(), labs() and llabs() including unit tests.
      implemented strrchr() including unit tests.
      fixed build dependencies for tests.
      added unit tests for already implemented str* functions.
      added mmap and munmap.
      added simple unit tests for already implemented mem* functions.

 Is there a way to fix this ?

2009/6/5 Henrique Almeida <hd...@gm...>

>
>  Ok, good idea, git branches rock !
>
> 2009/6/5 Andreas Krennmair <akr...@go...>
>
>> Hello everybody,
>>
>> As the "broken" branch didn't work out as expected, I found a better way
>> that both satisfies me in its abilities and also allows other developers to
>> easily see and merge my changes. I have a fork of libposix uploaded on
>> GitHub: http://github.com/akrennmair/libposix/tree/master
>> In this fork, I will regularly keep track of changes in the official
>> libposix git repository. But it's also simple to merge my commits into the
>> official libposix repository by executing
>> git pull git://github.com/akrennmair/libposix.git master
>> in a clone of the official libposix git repository. Anyway, GitHub is the
>> place to see and track my changes. Of course, this shall NOT be interpreted
>> as a way to get independent from the official project, it is merely a way
>> that helps me work in a more flexible fashion on the things that I want to
>> work on, plus it makes my changes more visible and also easier to
>> reintegrate with the official development line.
>>
>> Nevertheless, I will continue posting short notifications about the things
>> I currently work on to keep everyone informed. So far, I've worked on some
>> simple functions including unit tests, and I hope to present a simple
>> implementation of malloc(), free(), realloc() and calloc() within a day or
>> two.
>>
>> Regards,
>> Andreas
>>
>>
>> ------------------------------------------------------------------------------
>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>> looking to deploy the next generation of Solaris that includes the latest
>> innovations from Sun and the OpenSource community. Download a copy and
>> enjoy capabilities such as Networking, Storage and Virtualization.
>> Go to: http://p.sf.net/sfu/opensolaris-get
>> _______________________________________________
>> Libposix-development mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>
>>
>
>
> --
> Henrique Dante de Almeida
> hd...@gm...
>



-- 
Henrique Dante de Almeida
hd...@gm...

Re: [libposix-development] My personal development branch

[Andreas K. <akr...@go...>]

If there are differences, you always need an extra merge commit, as far as I
understand.

On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...> wrote:

>
>  With git pull, I'm not being able to merge each commit individually in my
> branch:
>
>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
> Merge: 1faac1a... 05b56ea...
> Author: Henrique <hd...@us...>
> Date:   Sat Jun 6 17:29:37 2009 -0300
>
>     Merge git://github.com/akrennmair/libposix into andreas
>
>     * git://github.com/akrennmair/libposix:
>       implemented abs(), labs() and llabs() including unit tests.
>       implemented strrchr() including unit tests.
>       fixed build dependencies for tests.
>       added unit tests for already implemented str* functions.
>       added mmap and munmap.
>       added simple unit tests for already implemented mem* functions.
>
>  Is there a way to fix this ?
>
> 2009/6/5 Henrique Almeida <hd...@gm...>
>
>
>>  Ok, good idea, git branches rock !
>>
>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>
>>> Hello everybody,
>>>
>>> As the "broken" branch didn't work out as expected, I found a better way
>>> that both satisfies me in its abilities and also allows other developers to
>>> easily see and merge my changes. I have a fork of libposix uploaded on
>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>> In this fork, I will regularly keep track of changes in the official
>>> libposix git repository. But it's also simple to merge my commits into the
>>> official libposix repository by executing
>>> git pull git://github.com/akrennmair/libposix.git master
>>> in a clone of the official libposix git repository. Anyway, GitHub is the
>>> place to see and track my changes. Of course, this shall NOT be interpreted
>>> as a way to get independent from the official project, it is merely a way
>>> that helps me work in a more flexible fashion on the things that I want to
>>> work on, plus it makes my changes more visible and also easier to
>>> reintegrate with the official development line.
>>>
>>> Nevertheless, I will continue posting short notifications about the
>>> things I currently work on to keep everyone informed. So far, I've worked on
>>> some simple functions including unit tests, and I hope to present a simple
>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>> two.
>>>
>>> Regards,
>>> Andreas
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>> looking to deploy the next generation of Solaris that includes the latest
>>> innovations from Sun and the OpenSource community. Download a copy and
>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>> _______________________________________________
>>> Libposix-development mailing list
>>> Lib...@li...
>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>
>>>
>>
>>
>> --
>> Henrique Dante de Almeida
>> hd...@gm...
>>
>
>
>
> --
> Henrique Dante de Almeida
> hd...@gm...
>
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>
>

Re: [libposix-development] My personal development branch

[Andreas K. <akr...@go...>]

Oh, BTW, I just saw that you moved all the string functions into a single
file. Generally, this is a bad idea. Eventually, libposix will not only have
a shared library version, but also a static library version, and in the
latter case, having each function in a separate source file (and thus in a
separate .o file) brings huge advantages, namely ld can automatically remove
.o files that aren't referenced. On the other hand, having each function
separated into an own file has no real disadvantage in a shared library (the
effects of inter-function optimizations are usually minimal if present at
all), plus having n separate files for n functions usually makes merges
easier than 1 or only a few files that contain everything.

Regards,
Andreas

On Mon, Jun 8, 2009 at 7:48 AM, Andreas Krennmair <akr...@go...
> wrote:

> If there are differences, you always need an extra merge commit, as far as
> I understand.
>
>
> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>wrote:
>
>>
>>  With git pull, I'm not being able to merge each commit individually in my
>> branch:
>>
>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>> Merge: 1faac1a... 05b56ea...
>> Author: Henrique <hd...@us...>
>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>
>>     Merge git://github.com/akrennmair/libposix into andreas
>>
>>     * git://github.com/akrennmair/libposix:
>>       implemented abs(), labs() and llabs() including unit tests.
>>       implemented strrchr() including unit tests.
>>       fixed build dependencies for tests.
>>       added unit tests for already implemented str* functions.
>>       added mmap and munmap.
>>       added simple unit tests for already implemented mem* functions.
>>
>>  Is there a way to fix this ?
>>
>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>
>>
>>>  Ok, good idea, git branches rock !
>>>
>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>
>>>> Hello everybody,
>>>>
>>>> As the "broken" branch didn't work out as expected, I found a better way
>>>> that both satisfies me in its abilities and also allows other developers to
>>>> easily see and merge my changes. I have a fork of libposix uploaded on
>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>> In this fork, I will regularly keep track of changes in the official
>>>> libposix git repository. But it's also simple to merge my commits into the
>>>> official libposix repository by executing
>>>> git pull git://github.com/akrennmair/libposix.git master
>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>> the place to see and track my changes. Of course, this shall NOT be
>>>> interpreted as a way to get independent from the official project, it is
>>>> merely a way that helps me work in a more flexible fashion on the things
>>>> that I want to work on, plus it makes my changes more visible and also
>>>> easier to reintegrate with the official development line.
>>>>
>>>> Nevertheless, I will continue posting short notifications about the
>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>> some simple functions including unit tests, and I hope to present a simple
>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>> two.
>>>>
>>>> Regards,
>>>> Andreas
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>> looking to deploy the next generation of Solaris that includes the
>>>> latest
>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>> _______________________________________________
>>>> Libposix-development mailing list
>>>> Lib...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>
>>>>
>>>
>>>
>>> --
>>> Henrique Dante de Almeida
>>> hd...@gm...
>>>
>>
>>
>>
>> --
>> Henrique Dante de Almeida
>> hd...@gm...
>>
>>
>> ------------------------------------------------------------------------------
>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>> looking to deploy the next generation of Solaris that includes the latest
>> innovations from Sun and the OpenSource community. Download a copy and
>> enjoy capabilities such as Networking, Storage and Virtualization.
>> Go to: http://p.sf.net/sfu/opensolaris-get
>> _______________________________________________
>> Libposix-development mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>
>>
>

Re: [libposix-development] My personal development branch

[Henrique A. <hd...@gm...>]

 I moved them because they're really small. The final source has 140 lines.
Since they're all mandatory functions we don't need modularity. In general
I'll favor easy code browsing over optimization. Source code or directory
splits should be done on demand whenever we find that it's necessary. I'm
pretty sure llvm LTO can remove isolated functions from the build, for
example. See:

 http://llvm.org/docs/LinkTimeOptimization.html

 We'll need to optimize for ld anyway at some moment, I can revert the
change if you bring me some reference saying that ld (or, say, objcopy)
can't do the same.

 PS: quick googling (concerning ld --gc-sections) suggest the opposite:


http://embeddedfreak.wordpress.com/2009/02/10/removing-unused-functionsdead-codes-with-gccgnu-ld/

2009/6/8 Andreas Krennmair <akr...@go...>

> Oh, BTW, I just saw that you moved all the string functions into a single
> file. Generally, this is a bad idea. Eventually, libposix will not only have
> a shared library version, but also a static library version, and in the
> latter case, having each function in a separate source file (and thus in a
> separate .o file) brings huge advantages, namely ld can automatically remove
> .o files that aren't referenced. On the other hand, having each function
> separated into an own file has no real disadvantage in a shared library (the
> effects of inter-function optimizations are usually minimal if present at
> all), plus having n separate files for n functions usually makes merges
> easier than 1 or only a few files that contain everything.
>
> Regards,
> Andreas
>
>
> On Mon, Jun 8, 2009 at 7:48 AM, Andreas Krennmair <
> akr...@go...> wrote:
>
>> If there are differences, you always need an extra merge commit, as far as
>> I understand.
>>
>>
>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>wrote:
>>
>>>
>>>  With git pull, I'm not being able to merge each commit individually in
>>> my branch:
>>>
>>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>>> Merge: 1faac1a... 05b56ea...
>>> Author: Henrique <hd...@us...>
>>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>>
>>>     Merge git://github.com/akrennmair/libposix into andreas
>>>
>>>     * git://github.com/akrennmair/libposix:
>>>       implemented abs(), labs() and llabs() including unit tests.
>>>       implemented strrchr() including unit tests.
>>>       fixed build dependencies for tests.
>>>       added unit tests for already implemented str* functions.
>>>       added mmap and munmap.
>>>       added simple unit tests for already implemented mem* functions.
>>>
>>>  Is there a way to fix this ?
>>>
>>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>>
>>>
>>>>  Ok, good idea, git branches rock !
>>>>
>>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>>
>>>>> Hello everybody,
>>>>>
>>>>> As the "broken" branch didn't work out as expected, I found a better
>>>>> way that both satisfies me in its abilities and also allows other developers
>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on
>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>>> In this fork, I will regularly keep track of changes in the official
>>>>> libposix git repository. But it's also simple to merge my commits into the
>>>>> official libposix repository by executing
>>>>> git pull git://github.com/akrennmair/libposix.git master
>>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>>> the place to see and track my changes. Of course, this shall NOT be
>>>>> interpreted as a way to get independent from the official project, it is
>>>>> merely a way that helps me work in a more flexible fashion on the things
>>>>> that I want to work on, plus it makes my changes more visible and also
>>>>> easier to reintegrate with the official development line.
>>>>>
>>>>> Nevertheless, I will continue posting short notifications about the
>>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>>> some simple functions including unit tests, and I hope to present a simple
>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>>> two.
>>>>>
>>>>> Regards,
>>>>> Andreas
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>> looking to deploy the next generation of Solaris that includes the
>>>>> latest
>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>> _______________________________________________
>>>>> Libposix-development mailing list
>>>>> Lib...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Henrique Dante de Almeida
>>>> hd...@gm...
>>>>
>>>
>>>
>>>
>>> --
>>> Henrique Dante de Almeida
>>> hd...@gm...
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>> looking to deploy the next generation of Solaris that includes the latest
>>> innovations from Sun and the OpenSource community. Download a copy and
>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>> _______________________________________________
>>> Libposix-development mailing list
>>> Lib...@li...
>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>
>>>
>>
>
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>
>


-- 
Henrique Dante de Almeida
hd...@gm...

Re: [libposix-development] My personal development branch

[Chris F. <ch...@fa...>]

I don't suppose its practical for us to compile a static library version
with -ffunction-sections, -fdata-sections [if using recent gcc] and
expect the library consumer to pass -gc-sections to ld?

That should get you the size advantages of putting things in their own
.o while not imposing anything on the source layout..

 

--Chris

 

From: Andreas Krennmair [mailto:akr...@go...] 
Sent: Monday, 8 June 2009 5:53 p.m.
To: lib...@li...
Subject: Re: [libposix-development] My personal development branch

 

Oh, BTW, I just saw that you moved all the string functions into a
single file. Generally, this is a bad idea. Eventually, libposix will
not only have a shared library version, but also a static library
version, and in the latter case, having each function in a separate
source file (and thus in a separate .o file) brings huge advantages,
namely ld can automatically remove .o files that aren't referenced. On
the other hand, having each function separated into an own file has no
real disadvantage in a shared library (the effects of inter-function
optimizations are usually minimal if present at all), plus having n
separate files for n functions usually makes merges easier than 1 or
only a few files that contain everything.

Regards,
Andreas

On Mon, Jun 8, 2009 at 7:48 AM, Andreas Krennmair
<akr...@go...> wrote:

If there are differences, you always need an extra merge commit, as far
as I understand.

 

On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>
wrote:


 With git pull, I'm not being able to merge each commit individually in
my branch:

 commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
Merge: 1faac1a... 05b56ea...
Author: Henrique <hd...@us...>
Date:   Sat Jun 6 17:29:37 2009 -0300

    Merge git://github.com/akrennmair/libposix into andreas
    
    * git://github.com/akrennmair/libposix:
      implemented abs(), labs() and llabs() including unit tests.
      implemented strrchr() including unit tests.
      fixed build dependencies for tests.
      added unit tests for already implemented str* functions.
      added mmap and munmap.
      added simple unit tests for already implemented mem* functions.

 Is there a way to fix this ?

2009/6/5 Henrique Almeida <hd...@gm...>

	 

	
	 Ok, good idea, git branches rock !

	2009/6/5 Andreas Krennmair <akr...@go...>

	Hello everybody,
	
	As the "broken" branch didn't work out as expected, I found a
better way that both satisfies me in its abilities and also allows other
developers to easily see and merge my changes. I have a fork of libposix
uploaded on GitHub: http://github.com/akrennmair/libposix/tree/master
	In this fork, I will regularly keep track of changes in the
official libposix git repository. But it's also simple to merge my
commits into the official libposix repository by executing
	git pull git://github.com/akrennmair/libposix.git master
	in a clone of the official libposix git repository. Anyway,
GitHub is the place to see and track my changes. Of course, this shall
NOT be interpreted as a way to get independent from the official
project, it is merely a way that helps me work in a more flexible
fashion on the things that I want to work on, plus it makes my changes
more visible and also easier to reintegrate with the official
development line.
	
	Nevertheless, I will continue posting short notifications about
the things I currently work on to keep everyone informed. So far, I've
worked on some simple functions including unit tests, and I hope to
present a simple implementation of malloc(), free(), realloc() and
calloc() within a day or two.
	
	Regards,
	Andreas

	
------------------------------------------------------------------------
------
	OpenSolaris 2009.06 is a cutting edge operating system for
enterprises
	looking to deploy the next generation of Solaris that includes
the latest
	innovations from Sun and the OpenSource community. Download a
copy and
	enjoy capabilities such as Networking, Storage and
Virtualization.
	Go to: http://p.sf.net/sfu/opensolaris-get
	_______________________________________________
	Libposix-development mailing list
	Lib...@li...
	
https://lists.sourceforge.net/lists/listinfo/libposix-development

	
	
	
	-- 
	Henrique Dante de Almeida
	hd...@gm...




-- 
Henrique Dante de Almeida
hd...@gm...


------------------------------------------------------------------------
------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the
latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
Libposix-development mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libposix-development

 

 

Re: [libposix-development] My personal development branch

[Andreas K. <akr...@go...>]

I wasn't talking about function and data sections, but about .o files only.
gcc and binutils support not including unreferenced .o files with .a files
for ages (I saw this the first time about 10 years ago).

Also, as I said, having one function per file usually makes merging easier.

Regards,
Andreas

On Mon, Jun 8, 2009 at 8:50 AM, Chris Forbes <ch...@fa...>wrote:

>  I don’t suppose its practical for us to compile a static library version
> with –ffunction-sections, -fdata-sections [if using recent gcc] and expect
> the library consumer to pass –gc-sections to ld?
>
> That should get you the size advantages of putting things in their own .o
> while not imposing anything on the source layout..
>
>
>
> --Chris
>
>
>
> *From:* Andreas Krennmair [mailto:akr...@go...]
> *Sent:* Monday, 8 June 2009 5:53 p.m.
> *To:* lib...@li...
> *Subject:* Re: [libposix-development] My personal development branch
>
>
>
> Oh, BTW, I just saw that you moved all the string functions into a single
> file. Generally, this is a bad idea. Eventually, libposix will not only have
> a shared library version, but also a static library version, and in the
> latter case, having each function in a separate source file (and thus in a
> separate .o file) brings huge advantages, namely ld can automatically remove
> .o files that aren't referenced. On the other hand, having each function
> separated into an own file has no real disadvantage in a shared library (the
> effects of inter-function optimizations are usually minimal if present at
> all), plus having n separate files for n functions usually makes merges
> easier than 1 or only a few files that contain everything.
>
> Regards,
> Andreas
>
> On Mon, Jun 8, 2009 at 7:48 AM, Andreas Krennmair <
> akr...@go...> wrote:
>
> If there are differences, you always need an extra merge commit, as far as
> I understand.
>
>
>
> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>
> wrote:
>
>
>  With git pull, I'm not being able to merge each commit individually in my
> branch:
>
>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
> Merge: 1faac1a... 05b56ea...
> Author: Henrique <hd...@us...>
> Date:   Sat Jun 6 17:29:37 2009 -0300
>
>     Merge git://github.com/akrennmair/libposix into andreas
>
>     * git://github.com/akrennmair/libposix:
>       implemented abs(), labs() and llabs() including unit tests.
>       implemented strrchr() including unit tests.
>       fixed build dependencies for tests.
>       added unit tests for already implemented str* functions.
>       added mmap and munmap.
>       added simple unit tests for already implemented mem* functions.
>
>  Is there a way to fix this ?
>
> 2009/6/5 Henrique Almeida <hd...@gm...>
>
>
>
>
>  Ok, good idea, git branches rock !
>
> 2009/6/5 Andreas Krennmair <akr...@go...>
>
> Hello everybody,
>
> As the "broken" branch didn't work out as expected, I found a better way
> that both satisfies me in its abilities and also allows other developers to
> easily see and merge my changes. I have a fork of libposix uploaded on
> GitHub: http://github.com/akrennmair/libposix/tree/master
> In this fork, I will regularly keep track of changes in the official
> libposix git repository. But it's also simple to merge my commits into the
> official libposix repository by executing
> git pull git://github.com/akrennmair/libposix.git master
> in a clone of the official libposix git repository. Anyway, GitHub is the
> place to see and track my changes. Of course, this shall NOT be interpreted
> as a way to get independent from the official project, it is merely a way
> that helps me work in a more flexible fashion on the things that I want to
> work on, plus it makes my changes more visible and also easier to
> reintegrate with the official development line.
>
> Nevertheless, I will continue posting short notifications about the things
> I currently work on to keep everyone informed. So far, I've worked on some
> simple functions including unit tests, and I hope to present a simple
> implementation of malloc(), free(), realloc() and calloc() within a day or
> two.
>
> Regards,
> Andreas
>
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>
>
>
>
> --
> Henrique Dante de Almeida
> hd...@gm...
>
>
>
>
> --
> Henrique Dante de Almeida
> hd...@gm...
>
>
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>
>

Re: [libposix-development] My personal development branch

[Henrique A. <hd...@gm...>]

 The problem was that the merge was condensed into a single commit (or maybe
I didn't notice the other commits in the log). I can try again later, but at
the moment there are some merge issues to resolve.

2009/6/8 Andreas Krennmair <akr...@go...>

> If there are differences, you always need an extra merge commit, as far as
> I understand.
>
>
> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>wrote:
>
>>
>>  With git pull, I'm not being able to merge each commit individually in my
>> branch:
>>
>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>> Merge: 1faac1a... 05b56ea...
>> Author: Henrique <hd...@us...>
>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>
>>     Merge git://github.com/akrennmair/libposix into andreas
>>
>>     * git://github.com/akrennmair/libposix:
>>       implemented abs(), labs() and llabs() including unit tests.
>>       implemented strrchr() including unit tests.
>>       fixed build dependencies for tests.
>>       added unit tests for already implemented str* functions.
>>       added mmap and munmap.
>>       added simple unit tests for already implemented mem* functions.
>>
>>  Is there a way to fix this ?
>>
>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>
>>
>>>  Ok, good idea, git branches rock !
>>>
>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>
>>>> Hello everybody,
>>>>
>>>> As the "broken" branch didn't work out as expected, I found a better way
>>>> that both satisfies me in its abilities and also allows other developers to
>>>> easily see and merge my changes. I have a fork of libposix uploaded on
>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>> In this fork, I will regularly keep track of changes in the official
>>>> libposix git repository. But it's also simple to merge my commits into the
>>>> official libposix repository by executing
>>>> git pull git://github.com/akrennmair/libposix.git master
>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>> the place to see and track my changes. Of course, this shall NOT be
>>>> interpreted as a way to get independent from the official project, it is
>>>> merely a way that helps me work in a more flexible fashion on the things
>>>> that I want to work on, plus it makes my changes more visible and also
>>>> easier to reintegrate with the official development line.
>>>>
>>>> Nevertheless, I will continue posting short notifications about the
>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>> some simple functions including unit tests, and I hope to present a simple
>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>> two.
>>>>
>>>> Regards,
>>>> Andreas
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>> looking to deploy the next generation of Solaris that includes the
>>>> latest
>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>> _______________________________________________
>>>> Libposix-development mailing list
>>>> Lib...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>
>>>>
>>>
>>>
>>> --
>>> Henrique Dante de Almeida
>>> hd...@gm...
>>>
>>
>>
>>
>> --
>> Henrique Dante de Almeida
>> hd...@gm...
>>
>>
>> ------------------------------------------------------------------------------
>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>> looking to deploy the next generation of Solaris that includes the latest
>> innovations from Sun and the OpenSource community. Download a copy and
>> enjoy capabilities such as Networking, Storage and Virtualization.
>> Go to: http://p.sf.net/sfu/opensolaris-get
>> _______________________________________________
>> Libposix-development mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>
>>
>
>
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
> looking to deploy the next generation of Solaris that includes the latest
> innovations from Sun and the OpenSource community. Download a copy and
> enjoy capabilities such as Networking, Storage and Virtualization.
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>
>


-- 
Henrique Dante de Almeida
hd...@gm...

Re: [libposix-development] My personal development branch

[Andreas K. <akr...@go...>]

No, all commits are included and kept separata (that's how it's supposed to
be, after all), sometimes you just need an additional merge commit that
fixes all the merge issues. It's as simple as that.

Regards,
Andreas

On Mon, Jun 8, 2009 at 5:24 PM, Henrique Almeida <hd...@gm...> wrote:

>
>  The problem was that the merge was condensed into a single commit (or
> maybe I didn't notice the other commits in the log). I can try again later,
> but at the moment there are some merge issues to resolve.
>
> 2009/6/8 Andreas Krennmair <akr...@go...>
>
> If there are differences, you always need an extra merge commit, as far as
>> I understand.
>>
>>
>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>wrote:
>>
>>>
>>>  With git pull, I'm not being able to merge each commit individually in
>>> my branch:
>>>
>>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>>> Merge: 1faac1a... 05b56ea...
>>> Author: Henrique <hd...@us...>
>>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>>
>>>     Merge git://github.com/akrennmair/libposix into andreas
>>>
>>>     * git://github.com/akrennmair/libposix:
>>>       implemented abs(), labs() and llabs() including unit tests.
>>>       implemented strrchr() including unit tests.
>>>       fixed build dependencies for tests.
>>>       added unit tests for already implemented str* functions.
>>>       added mmap and munmap.
>>>       added simple unit tests for already implemented mem* functions.
>>>
>>>  Is there a way to fix this ?
>>>
>>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>>
>>>
>>>>  Ok, good idea, git branches rock !
>>>>
>>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>>
>>>>> Hello everybody,
>>>>>
>>>>> As the "broken" branch didn't work out as expected, I found a better
>>>>> way that both satisfies me in its abilities and also allows other developers
>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on
>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>>> In this fork, I will regularly keep track of changes in the official
>>>>> libposix git repository. But it's also simple to merge my commits into the
>>>>> official libposix repository by executing
>>>>> git pull git://github.com/akrennmair/libposix.git master
>>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>>> the place to see and track my changes. Of course, this shall NOT be
>>>>> interpreted as a way to get independent from the official project, it is
>>>>> merely a way that helps me work in a more flexible fashion on the things
>>>>> that I want to work on, plus it makes my changes more visible and also
>>>>> easier to reintegrate with the official development line.
>>>>>
>>>>> Nevertheless, I will continue posting short notifications about the
>>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>>> some simple functions including unit tests, and I hope to present a simple
>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>>> two.
>>>>>
>>>>> Regards,
>>>>> Andreas
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>> looking to deploy the next generation of Solaris that includes the
>>>>> latest
>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>> _______________________________________________
>>>>> Libposix-development mailing list
>>>>> Lib...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Henrique Dante de Almeida
>>>> hd...@gm...
>>>>
>>>
>>>
>>>
>>> --
>>> Henrique Dante de Almeida
>>> hd...@gm...
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>> looking to deploy the next generation of Solaris that includes the latest
>>> innovations from Sun and the OpenSource community. Download a copy and
>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>> _______________________________________________
>>> Libposix-development mailing list
>>> Lib...@li...
>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>> looking to deploy the next generation of Solaris that includes the latest
>> innovations from Sun and the OpenSource community. Download a copy and
>> enjoy capabilities such as Networking, Storage and Virtualization.
>> Go to: http://p.sf.net/sfu/opensolaris-get
>> _______________________________________________
>> Libposix-development mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>
>>
>
>
> --
> Henrique Dante de Almeida
> hd...@gm...
>
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>
>

Re: [libposix-development] My personal development branch

[Henrique A. <hd...@gm...>]

 I have done a git pull here and there are individual commits. I think I
haven't noticed them earlier. I'll begin to read each of them.

2009/6/8 Henrique Almeida <hd...@gm...>

>
>  The problem was that the merge was condensed into a single commit (or
> maybe I didn't notice the other commits in the log). I can try again later,
> but at the moment there are some merge issues to resolve.
>
> 2009/6/8 Andreas Krennmair <akr...@go...>
>
> If there are differences, you always need an extra merge commit, as far as
>> I understand.
>>
>>
>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>wrote:
>>
>>>
>>>  With git pull, I'm not being able to merge each commit individually in
>>> my branch:
>>>
>>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>>> Merge: 1faac1a... 05b56ea...
>>> Author: Henrique <hd...@us...>
>>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>>
>>>     Merge git://github.com/akrennmair/libposix into andreas
>>>
>>>     * git://github.com/akrennmair/libposix:
>>>       implemented abs(), labs() and llabs() including unit tests.
>>>       implemented strrchr() including unit tests.
>>>       fixed build dependencies for tests.
>>>       added unit tests for already implemented str* functions.
>>>       added mmap and munmap.
>>>       added simple unit tests for already implemented mem* functions.
>>>
>>>  Is there a way to fix this ?
>>>
>>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>>
>>>
>>>>  Ok, good idea, git branches rock !
>>>>
>>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>>
>>>>> Hello everybody,
>>>>>
>>>>> As the "broken" branch didn't work out as expected, I found a better
>>>>> way that both satisfies me in its abilities and also allows other developers
>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on
>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>>> In this fork, I will regularly keep track of changes in the official
>>>>> libposix git repository. But it's also simple to merge my commits into the
>>>>> official libposix repository by executing
>>>>> git pull git://github.com/akrennmair/libposix.git master
>>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>>> the place to see and track my changes. Of course, this shall NOT be
>>>>> interpreted as a way to get independent from the official project, it is
>>>>> merely a way that helps me work in a more flexible fashion on the things
>>>>> that I want to work on, plus it makes my changes more visible and also
>>>>> easier to reintegrate with the official development line.
>>>>>
>>>>> Nevertheless, I will continue posting short notifications about the
>>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>>> some simple functions including unit tests, and I hope to present a simple
>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>>> two.
>>>>>
>>>>> Regards,
>>>>> Andreas
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>> looking to deploy the next generation of Solaris that includes the
>>>>> latest
>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>> _______________________________________________
>>>>> Libposix-development mailing list
>>>>> Lib...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Henrique Dante de Almeida
>>>> hd...@gm...
>>>>
>>>
>>>
>>>
>>> --
>>> Henrique Dante de Almeida
>>> hd...@gm...
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>> looking to deploy the next generation of Solaris that includes the latest
>>> innovations from Sun and the OpenSource community. Download a copy and
>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>> _______________________________________________
>>> Libposix-development mailing list
>>> Lib...@li...
>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>> looking to deploy the next generation of Solaris that includes the latest
>> innovations from Sun and the OpenSource community. Download a copy and
>> enjoy capabilities such as Networking, Storage and Virtualization.
>> Go to: http://p.sf.net/sfu/opensolaris-get
>> _______________________________________________
>> Libposix-development mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>
>>
>
>
> --
> Henrique Dante de Almeida
> hd...@gm...
>



-- 
Henrique Dante de Almeida
hd...@gm...

Re: [libposix-development] My personal development branch

[Henrique A. <hd...@gm...>]

 Comments for commit:

 1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap.

- sys/mman.h
 - the PROT_* macros are system dependent (they depend on the kernel used).
   mman.h should be moved to the system directory. Also, the reference for
   the values for linux are missing.


2009/6/9 Henrique Almeida <hd...@gm...>:
>
>  I have done a git pull here and there are individual commits. I think I
> haven't noticed them earlier. I'll begin to read each of them.
>
> 2009/6/8 Henrique Almeida <hd...@gm...>
>>
>>  The problem was that the merge was condensed into a single commit (or
>> maybe I didn't notice the other commits in the log). I can try again later,
>> but at the moment there are some merge issues to resolve.
>>
>> 2009/6/8 Andreas Krennmair <akr...@go...>
>>>
>>> If there are differences, you always need an extra merge commit, as far
>>> as I understand.
>>>
>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>
>>> wrote:
>>>>
>>>>  With git pull, I'm not being able to merge each commit individually in
>>>> my branch:
>>>>
>>>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>>>> Merge: 1faac1a... 05b56ea...
>>>> Author: Henrique <hd...@us...>
>>>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>>>
>>>>     Merge git://github.com/akrennmair/libposix into andreas
>>>>
>>>>     * git://github.com/akrennmair/libposix:
>>>>       implemented abs(), labs() and llabs() including unit tests.
>>>>       implemented strrchr() including unit tests.
>>>>       fixed build dependencies for tests.
>>>>       added unit tests for already implemented str* functions.
>>>>       added mmap and munmap.
>>>>       added simple unit tests for already implemented mem* functions.
>>>>
>>>>  Is there a way to fix this ?
>>>>
>>>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>>>>
>>>>>  Ok, good idea, git branches rock !
>>>>>
>>>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>>>>
>>>>>> Hello everybody,
>>>>>>
>>>>>> As the "broken" branch didn't work out as expected, I found a better
>>>>>> way that both satisfies me in its abilities and also allows other developers
>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on
>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>>>> In this fork, I will regularly keep track of changes in the official
>>>>>> libposix git repository. But it's also simple to merge my commits into the
>>>>>> official libposix repository by executing
>>>>>> git pull git://github.com/akrennmair/libposix.git master
>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>>>> the place to see and track my changes. Of course, this shall NOT be
>>>>>> interpreted as a way to get independent from the official project, it is
>>>>>> merely a way that helps me work in a more flexible fashion on the things
>>>>>> that I want to work on, plus it makes my changes more visible and also
>>>>>> easier to reintegrate with the official development line.
>>>>>>
>>>>>> Nevertheless, I will continue posting short notifications about the
>>>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>>>> some simple functions including unit tests, and I hope to present a simple
>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>>>> two.
>>>>>>
>>>>>> Regards,
>>>>>> Andreas
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>> latest
>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>> _______________________________________________
>>>>>> Libposix-development mailing list
>>>>>> Lib...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Henrique Dante de Almeida
>>>>> hd...@gm...
>>>>
>>>>
>>>>
>>>> --
>>>> Henrique Dante de Almeida
>>>> hd...@gm...
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>> looking to deploy the next generation of Solaris that includes the
>>>> latest
>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>> _______________________________________________
>>>> Libposix-development mailing list
>>>> Lib...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>> looking to deploy the next generation of Solaris that includes the latest
>>> innovations from Sun and the OpenSource community. Download a copy and
>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>> _______________________________________________
>>> Libposix-development mailing list
>>> Lib...@li...
>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>
>>
>>
>>
>> --
>> Henrique Dante de Almeida
>> hd...@gm...
>
>
>
> --
> Henrique Dante de Almeida
> hd...@gm...
>



-- 
 Henrique Dante de Almeida
 hd...@gm...

Re: [libposix-development] My personal development branch

[Henrique A. <hd...@gm...>]

 Comments for commit:

 d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already
implemented str* functions.

 - remove test prefix from file names
- test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is
incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13
- add test coverage to strcmp: range 0, UCHAR_MAX
- add test coverage to strcpy: out of bound writes (both sides)


2009/6/9 Henrique Almeida <hd...@gm...>:
>  Comments for commit:
>
>  1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap.
>
> - sys/mman.h
>  - the PROT_* macros are system dependent (they depend on the kernel used).
>   mman.h should be moved to the system directory. Also, the reference for
>   the values for linux are missing.
>
>
> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>
>>  I have done a git pull here and there are individual commits. I think I
>> haven't noticed them earlier. I'll begin to read each of them.
>>
>> 2009/6/8 Henrique Almeida <hd...@gm...>
>>>
>>>  The problem was that the merge was condensed into a single commit (or
>>> maybe I didn't notice the other commits in the log). I can try again later,
>>> but at the moment there are some merge issues to resolve.
>>>
>>> 2009/6/8 Andreas Krennmair <akr...@go...>
>>>>
>>>> If there are differences, you always need an extra merge commit, as far
>>>> as I understand.
>>>>
>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>
>>>> wrote:
>>>>>
>>>>>  With git pull, I'm not being able to merge each commit individually in
>>>>> my branch:
>>>>>
>>>>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>>>>> Merge: 1faac1a... 05b56ea...
>>>>> Author: Henrique <hd...@us...>
>>>>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>>>>
>>>>>     Merge git://github.com/akrennmair/libposix into andreas
>>>>>
>>>>>     * git://github.com/akrennmair/libposix:
>>>>>       implemented abs(), labs() and llabs() including unit tests.
>>>>>       implemented strrchr() including unit tests.
>>>>>       fixed build dependencies for tests.
>>>>>       added unit tests for already implemented str* functions.
>>>>>       added mmap and munmap.
>>>>>       added simple unit tests for already implemented mem* functions.
>>>>>
>>>>>  Is there a way to fix this ?
>>>>>
>>>>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>>>>>
>>>>>>  Ok, good idea, git branches rock !
>>>>>>
>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>>>>>
>>>>>>> Hello everybody,
>>>>>>>
>>>>>>> As the "broken" branch didn't work out as expected, I found a better
>>>>>>> way that both satisfies me in its abilities and also allows other developers
>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on
>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>>>>> In this fork, I will regularly keep track of changes in the official
>>>>>>> libposix git repository. But it's also simple to merge my commits into the
>>>>>>> official libposix repository by executing
>>>>>>> git pull git://github.com/akrennmair/libposix.git master
>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>>>>> the place to see and track my changes. Of course, this shall NOT be
>>>>>>> interpreted as a way to get independent from the official project, it is
>>>>>>> merely a way that helps me work in a more flexible fashion on the things
>>>>>>> that I want to work on, plus it makes my changes more visible and also
>>>>>>> easier to reintegrate with the official development line.
>>>>>>>
>>>>>>> Nevertheless, I will continue posting short notifications about the
>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>>>>> some simple functions including unit tests, and I hope to present a simple
>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>>>>> two.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Andreas
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>> latest
>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>> _______________________________________________
>>>>>>> Libposix-development mailing list
>>>>>>> Lib...@li...
>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Henrique Dante de Almeida
>>>>>> hd...@gm...
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Henrique Dante de Almeida
>>>>> hd...@gm...
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>> looking to deploy the next generation of Solaris that includes the
>>>>> latest
>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>> _______________________________________________
>>>>> Libposix-development mailing list
>>>>> Lib...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>> looking to deploy the next generation of Solaris that includes the latest
>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>> _______________________________________________
>>>> Libposix-development mailing list
>>>> Lib...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>
>>>
>>>
>>>
>>> --
>>> Henrique Dante de Almeida
>>> hd...@gm...
>>
>>
>>
>> --
>> Henrique Dante de Almeida
>> hd...@gm...
>>
>
>
>
> --
>  Henrique Dante de Almeida
>  hd...@gm...
>



-- 
 Henrique Dante de Almeida
 hd...@gm...

Re: [libposix-development] My personal development branch

[Henrique A. <hd...@gm...>]

 Comments for commit:

 3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr()
including unit tests.

 on strrchr.c, '\0' must be considered part of the string, fix both
the implementation and test

2009/6/9 Henrique Almeida <hd...@gm...>:
>  Comments for commit:
>
>  d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already
> implemented str* functions.
>
>  - remove test prefix from file names
> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is
> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13
> - add test coverage to strcmp: range 0, UCHAR_MAX
> - add test coverage to strcpy: out of bound writes (both sides)
>
>
> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>  Comments for commit:
>>
>>  1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap.
>>
>> - sys/mman.h
>>  - the PROT_* macros are system dependent (they depend on the kernel used).
>>   mman.h should be moved to the system directory. Also, the reference for
>>   the values for linux are missing.
>>
>>
>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>
>>>  I have done a git pull here and there are individual commits. I think I
>>> haven't noticed them earlier. I'll begin to read each of them.
>>>
>>> 2009/6/8 Henrique Almeida <hd...@gm...>
>>>>
>>>>  The problem was that the merge was condensed into a single commit (or
>>>> maybe I didn't notice the other commits in the log). I can try again later,
>>>> but at the moment there are some merge issues to resolve.
>>>>
>>>> 2009/6/8 Andreas Krennmair <akr...@go...>
>>>>>
>>>>> If there are differences, you always need an extra merge commit, as far
>>>>> as I understand.
>>>>>
>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>
>>>>> wrote:
>>>>>>
>>>>>>  With git pull, I'm not being able to merge each commit individually in
>>>>>> my branch:
>>>>>>
>>>>>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>>>>>> Merge: 1faac1a... 05b56ea...
>>>>>> Author: Henrique <hd...@us...>
>>>>>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>>>>>
>>>>>>     Merge git://github.com/akrennmair/libposix into andreas
>>>>>>
>>>>>>     * git://github.com/akrennmair/libposix:
>>>>>>       implemented abs(), labs() and llabs() including unit tests.
>>>>>>       implemented strrchr() including unit tests.
>>>>>>       fixed build dependencies for tests.
>>>>>>       added unit tests for already implemented str* functions.
>>>>>>       added mmap and munmap.
>>>>>>       added simple unit tests for already implemented mem* functions.
>>>>>>
>>>>>>  Is there a way to fix this ?
>>>>>>
>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>>>>>>
>>>>>>>  Ok, good idea, git branches rock !
>>>>>>>
>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>>>>>>
>>>>>>>> Hello everybody,
>>>>>>>>
>>>>>>>> As the "broken" branch didn't work out as expected, I found a better
>>>>>>>> way that both satisfies me in its abilities and also allows other developers
>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on
>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>>>>>> In this fork, I will regularly keep track of changes in the official
>>>>>>>> libposix git repository. But it's also simple to merge my commits into the
>>>>>>>> official libposix repository by executing
>>>>>>>> git pull git://github.com/akrennmair/libposix.git master
>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>>>>>> the place to see and track my changes. Of course, this shall NOT be
>>>>>>>> interpreted as a way to get independent from the official project, it is
>>>>>>>> merely a way that helps me work in a more flexible fashion on the things
>>>>>>>> that I want to work on, plus it makes my changes more visible and also
>>>>>>>> easier to reintegrate with the official development line.
>>>>>>>>
>>>>>>>> Nevertheless, I will continue posting short notifications about the
>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>>>>>> some simple functions including unit tests, and I hope to present a simple
>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>>>>>> two.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Andreas
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>> latest
>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>> _______________________________________________
>>>>>>>> Libposix-development mailing list
>>>>>>>> Lib...@li...
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Henrique Dante de Almeida
>>>>>>> hd...@gm...
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Henrique Dante de Almeida
>>>>>> hd...@gm...
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>> latest
>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>> _______________________________________________
>>>>>> Libposix-development mailing list
>>>>>> Lib...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>> looking to deploy the next generation of Solaris that includes the latest
>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>> _______________________________________________
>>>>> Libposix-development mailing list
>>>>> Lib...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Henrique Dante de Almeida
>>>> hd...@gm...
>>>
>>>
>>>
>>> --
>>> Henrique Dante de Almeida
>>> hd...@gm...
>>>
>>
>>
>>
>> --
>>  Henrique Dante de Almeida
>>  hd...@gm...
>>
>
>
>
> --
>  Henrique Dante de Almeida
>  hd...@gm...
>



-- 
 Henrique Dante de Almeida
 hd...@gm...

Re: [libposix-development] My personal development branch

[Henrique A. <hd...@gm...>]

 Broken branch updated up to 2009-06-05

2009/6/9 Henrique Almeida <hd...@gm...>:
>  Comments for commit:
>
>  3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr()
> including unit tests.
>
>  on strrchr.c, '\0' must be considered part of the string, fix both
> the implementation and test
>
> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>  Comments for commit:
>>
>>  d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already
>> implemented str* functions.
>>
>>  - remove test prefix from file names
>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is
>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13
>> - add test coverage to strcmp: range 0, UCHAR_MAX
>> - add test coverage to strcpy: out of bound writes (both sides)
>>
>>
>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>  Comments for commit:
>>>
>>>  1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap.
>>>
>>> - sys/mman.h
>>>  - the PROT_* macros are system dependent (they depend on the kernel used).
>>>   mman.h should be moved to the system directory. Also, the reference for
>>>   the values for linux are missing.
>>>
>>>
>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>
>>>>  I have done a git pull here and there are individual commits. I think I
>>>> haven't noticed them earlier. I'll begin to read each of them.
>>>>
>>>> 2009/6/8 Henrique Almeida <hd...@gm...>
>>>>>
>>>>>  The problem was that the merge was condensed into a single commit (or
>>>>> maybe I didn't notice the other commits in the log). I can try again later,
>>>>> but at the moment there are some merge issues to resolve.
>>>>>
>>>>> 2009/6/8 Andreas Krennmair <akr...@go...>
>>>>>>
>>>>>> If there are differences, you always need an extra merge commit, as far
>>>>>> as I understand.
>>>>>>
>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>
>>>>>> wrote:
>>>>>>>
>>>>>>>  With git pull, I'm not being able to merge each commit individually in
>>>>>>> my branch:
>>>>>>>
>>>>>>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>>>>>>> Merge: 1faac1a... 05b56ea...
>>>>>>> Author: Henrique <hd...@us...>
>>>>>>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>>>>>>
>>>>>>>     Merge git://github.com/akrennmair/libposix into andreas
>>>>>>>
>>>>>>>     * git://github.com/akrennmair/libposix:
>>>>>>>       implemented abs(), labs() and llabs() including unit tests.
>>>>>>>       implemented strrchr() including unit tests.
>>>>>>>       fixed build dependencies for tests.
>>>>>>>       added unit tests for already implemented str* functions.
>>>>>>>       added mmap and munmap.
>>>>>>>       added simple unit tests for already implemented mem* functions.
>>>>>>>
>>>>>>>  Is there a way to fix this ?
>>>>>>>
>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>>>>>>>
>>>>>>>>  Ok, good idea, git branches rock !
>>>>>>>>
>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>>>>>>>
>>>>>>>>> Hello everybody,
>>>>>>>>>
>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better
>>>>>>>>> way that both satisfies me in its abilities and also allows other developers
>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on
>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>>>>>>> In this fork, I will regularly keep track of changes in the official
>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the
>>>>>>>>> official libposix repository by executing
>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master
>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be
>>>>>>>>> interpreted as a way to get independent from the official project, it is
>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things
>>>>>>>>> that I want to work on, plus it makes my changes more visible and also
>>>>>>>>> easier to reintegrate with the official development line.
>>>>>>>>>
>>>>>>>>> Nevertheless, I will continue posting short notifications about the
>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>>>>>>> some simple functions including unit tests, and I hope to present a simple
>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>>>>>>> two.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Andreas
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>> latest
>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>> _______________________________________________
>>>>>>>>> Libposix-development mailing list
>>>>>>>>> Lib...@li...
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Henrique Dante de Almeida
>>>>>>>> hd...@gm...
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Henrique Dante de Almeida
>>>>>>> hd...@gm...
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>> latest
>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>> _______________________________________________
>>>>>>> Libposix-development mailing list
>>>>>>> Lib...@li...
>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>> looking to deploy the next generation of Solaris that includes the latest
>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>> _______________________________________________
>>>>>> Libposix-development mailing list
>>>>>> Lib...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Henrique Dante de Almeida
>>>>> hd...@gm...
>>>>
>>>>
>>>>
>>>> --
>>>> Henrique Dante de Almeida
>>>> hd...@gm...
>>>>
>>>
>>>
>>>
>>> --
>>>  Henrique Dante de Almeida
>>>  hd...@gm...
>>>
>>
>>
>>
>> --
>>  Henrique Dante de Almeida
>>  hd...@gm...
>>
>
>
>
> --
>  Henrique Dante de Almeida
>  hd...@gm...
>



-- 
 Henrique Dante de Almeida
 hd...@gm...

Re: [libposix-development] My personal development branch

[Henrique A. <hd...@gm...>]

 Comments for commit:

 9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build.

 - uncomment #ifdef in syscall_nums.h
 - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi

2009/6/9 Henrique Almeida <hd...@gm...>:
>  Broken branch updated up to 2009-06-05
>
> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>  Comments for commit:
>>
>>  3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr()
>> including unit tests.
>>
>>  on strrchr.c, '\0' must be considered part of the string, fix both
>> the implementation and test
>>
>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>  Comments for commit:
>>>
>>>  d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already
>>> implemented str* functions.
>>>
>>>  - remove test prefix from file names
>>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is
>>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13
>>> - add test coverage to strcmp: range 0, UCHAR_MAX
>>> - add test coverage to strcpy: out of bound writes (both sides)
>>>
>>>
>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>  Comments for commit:
>>>>
>>>>  1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap.
>>>>
>>>> - sys/mman.h
>>>>  - the PROT_* macros are system dependent (they depend on the kernel used).
>>>>   mman.h should be moved to the system directory. Also, the reference for
>>>>   the values for linux are missing.
>>>>
>>>>
>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>
>>>>>  I have done a git pull here and there are individual commits. I think I
>>>>> haven't noticed them earlier. I'll begin to read each of them.
>>>>>
>>>>> 2009/6/8 Henrique Almeida <hd...@gm...>
>>>>>>
>>>>>>  The problem was that the merge was condensed into a single commit (or
>>>>>> maybe I didn't notice the other commits in the log). I can try again later,
>>>>>> but at the moment there are some merge issues to resolve.
>>>>>>
>>>>>> 2009/6/8 Andreas Krennmair <akr...@go...>
>>>>>>>
>>>>>>> If there are differences, you always need an extra merge commit, as far
>>>>>>> as I understand.
>>>>>>>
>>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>  With git pull, I'm not being able to merge each commit individually in
>>>>>>>> my branch:
>>>>>>>>
>>>>>>>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>>>>>>>> Merge: 1faac1a... 05b56ea...
>>>>>>>> Author: Henrique <hd...@us...>
>>>>>>>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>>>>>>>
>>>>>>>>     Merge git://github.com/akrennmair/libposix into andreas
>>>>>>>>
>>>>>>>>     * git://github.com/akrennmair/libposix:
>>>>>>>>       implemented abs(), labs() and llabs() including unit tests.
>>>>>>>>       implemented strrchr() including unit tests.
>>>>>>>>       fixed build dependencies for tests.
>>>>>>>>       added unit tests for already implemented str* functions.
>>>>>>>>       added mmap and munmap.
>>>>>>>>       added simple unit tests for already implemented mem* functions.
>>>>>>>>
>>>>>>>>  Is there a way to fix this ?
>>>>>>>>
>>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>>>>>>>>
>>>>>>>>>  Ok, good idea, git branches rock !
>>>>>>>>>
>>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>>>>>>>>
>>>>>>>>>> Hello everybody,
>>>>>>>>>>
>>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better
>>>>>>>>>> way that both satisfies me in its abilities and also allows other developers
>>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on
>>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>>>>>>>> In this fork, I will regularly keep track of changes in the official
>>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the
>>>>>>>>>> official libposix repository by executing
>>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master
>>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be
>>>>>>>>>> interpreted as a way to get independent from the official project, it is
>>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things
>>>>>>>>>> that I want to work on, plus it makes my changes more visible and also
>>>>>>>>>> easier to reintegrate with the official development line.
>>>>>>>>>>
>>>>>>>>>> Nevertheless, I will continue posting short notifications about the
>>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>>>>>>>> some simple functions including unit tests, and I hope to present a simple
>>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>>>>>>>> two.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Andreas
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>>> latest
>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>> Lib...@li...
>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>> hd...@gm...
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Henrique Dante de Almeida
>>>>>>>> hd...@gm...
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>> latest
>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>> _______________________________________________
>>>>>>>> Libposix-development mailing list
>>>>>>>> Lib...@li...
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>> looking to deploy the next generation of Solaris that includes the latest
>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>> _______________________________________________
>>>>>>> Libposix-development mailing list
>>>>>>> Lib...@li...
>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Henrique Dante de Almeida
>>>>>> hd...@gm...
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Henrique Dante de Almeida
>>>>> hd...@gm...
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>  Henrique Dante de Almeida
>>>>  hd...@gm...
>>>>
>>>
>>>
>>>
>>> --
>>>  Henrique Dante de Almeida
>>>  hd...@gm...
>>>
>>
>>
>>
>> --
>>  Henrique Dante de Almeida
>>  hd...@gm...
>>
>
>
>
> --
>  Henrique Dante de Almeida
>  hd...@gm...
>



-- 
 Henrique Dante de Almeida
 hd...@gm...

Re: [libposix-development] My personal development branch

[Henrique A. <hd...@gm...>]

 Comments for commit:

1e39bb5359952c6c6e28cc74f6651c98c8d86905 added auto-generated system
calls (including auto-generator script).

signal.h:
- the "include" files can't contain conditional code (_WORDSIZE),
move signal.h to system specific directories (or add an #include
<arch_signal.h>)
stat.h:
- __pad0, __st_ino, etc. where did those come from ?
- can't have __attribute__ extension in "include" directory (where
  did those come from ?)
- sigval_t this doesn't exist in the standard

Are you copying this from an older implementation ? There are too many
unexpected features in this patch. I need to understand what's this
all about before I continue reading the patches. I can't spend time
verifying that non standard code is being submitted, this has to be
done by the contributor.

2009/6/12 Henrique Almeida <hd...@gm...>:
>  Comments for commit:
>
>  9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build.
>
>  - uncomment #ifdef in syscall_nums.h
>  - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi
>
> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>  Broken branch updated up to 2009-06-05
>>
>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>  Comments for commit:
>>>
>>>  3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr()
>>> including unit tests.
>>>
>>>  on strrchr.c, '\0' must be considered part of the string, fix both
>>> the implementation and test
>>>
>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>  Comments for commit:
>>>>
>>>>  d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already
>>>> implemented str* functions.
>>>>
>>>>  - remove test prefix from file names
>>>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is
>>>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13
>>>> - add test coverage to strcmp: range 0, UCHAR_MAX
>>>> - add test coverage to strcpy: out of bound writes (both sides)
>>>>
>>>>
>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>  Comments for commit:
>>>>>
>>>>>  1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap.
>>>>>
>>>>> - sys/mman.h
>>>>>  - the PROT_* macros are system dependent (they depend on the kernel used).
>>>>>   mman.h should be moved to the system directory. Also, the reference for
>>>>>   the values for linux are missing.
>>>>>
>>>>>
>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>
>>>>>>  I have done a git pull here and there are individual commits. I think I
>>>>>> haven't noticed them earlier. I'll begin to read each of them.
>>>>>>
>>>>>> 2009/6/8 Henrique Almeida <hd...@gm...>
>>>>>>>
>>>>>>>  The problem was that the merge was condensed into a single commit (or
>>>>>>> maybe I didn't notice the other commits in the log). I can try again later,
>>>>>>> but at the moment there are some merge issues to resolve.
>>>>>>>
>>>>>>> 2009/6/8 Andreas Krennmair <akr...@go...>
>>>>>>>>
>>>>>>>> If there are differences, you always need an extra merge commit, as far
>>>>>>>> as I understand.
>>>>>>>>
>>>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>  With git pull, I'm not being able to merge each commit individually in
>>>>>>>>> my branch:
>>>>>>>>>
>>>>>>>>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>>>>>>>>> Merge: 1faac1a... 05b56ea...
>>>>>>>>> Author: Henrique <hd...@us...>
>>>>>>>>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>>>>>>>>
>>>>>>>>>     Merge git://github.com/akrennmair/libposix into andreas
>>>>>>>>>
>>>>>>>>>     * git://github.com/akrennmair/libposix:
>>>>>>>>>       implemented abs(), labs() and llabs() including unit tests.
>>>>>>>>>       implemented strrchr() including unit tests.
>>>>>>>>>       fixed build dependencies for tests.
>>>>>>>>>       added unit tests for already implemented str* functions.
>>>>>>>>>       added mmap and munmap.
>>>>>>>>>       added simple unit tests for already implemented mem* functions.
>>>>>>>>>
>>>>>>>>>  Is there a way to fix this ?
>>>>>>>>>
>>>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>>>>>>>>>
>>>>>>>>>>  Ok, good idea, git branches rock !
>>>>>>>>>>
>>>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>>>>>>>>>
>>>>>>>>>>> Hello everybody,
>>>>>>>>>>>
>>>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better
>>>>>>>>>>> way that both satisfies me in its abilities and also allows other developers
>>>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on
>>>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>>>>>>>>> In this fork, I will regularly keep track of changes in the official
>>>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the
>>>>>>>>>>> official libposix repository by executing
>>>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master
>>>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be
>>>>>>>>>>> interpreted as a way to get independent from the official project, it is
>>>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things
>>>>>>>>>>> that I want to work on, plus it makes my changes more visible and also
>>>>>>>>>>> easier to reintegrate with the official development line.
>>>>>>>>>>>
>>>>>>>>>>> Nevertheless, I will continue posting short notifications about the
>>>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>>>>>>>>> some simple functions including unit tests, and I hope to present a simple
>>>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>>>>>>>>> two.
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Andreas
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>>>> latest
>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>> Lib...@li...
>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>> hd...@gm...
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>> hd...@gm...
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>> latest
>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>> _______________________________________________
>>>>>>>>> Libposix-development mailing list
>>>>>>>>> Lib...@li...
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>> looking to deploy the next generation of Solaris that includes the latest
>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>> _______________________________________________
>>>>>>>> Libposix-development mailing list
>>>>>>>> Lib...@li...
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Henrique Dante de Almeida
>>>>>>> hd...@gm...
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Henrique Dante de Almeida
>>>>>> hd...@gm...
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>  Henrique Dante de Almeida
>>>>>  hd...@gm...
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>  Henrique Dante de Almeida
>>>>  hd...@gm...
>>>>
>>>
>>>
>>>
>>> --
>>>  Henrique Dante de Almeida
>>>  hd...@gm...
>>>
>>
>>
>>
>> --
>>  Henrique Dante de Almeida
>>  hd...@gm...
>>
>
>
>
> --
>  Henrique Dante de Almeida
>  hd...@gm...
>



-- 
 Henrique Dante de Almeida
 hd...@gm...

Re: [libposix-development] My personal development branch

[Andreas K. <akr...@go...>]

Henrique,

I'm not pulling the struct definition out of my a**, Linux is the way
it is (especially its kernel data structures), and there's nothing
that can be changed about it from my side. If this is unacceptable,
well, then I can't help you. Take the code or leave it, it's all your
decision. Having to vindicate every single line of code that I
contribute isn't exactly something that makes me eager to contribute
more code.

Best regards,
Andreas

On Sat, Jun 13, 2009 at 5:21 AM, Henrique Almeida<hd...@gm...> wrote:
>  Comments for commit:
>
> 1e39bb5359952c6c6e28cc74f6651c98c8d86905 added auto-generated system
> calls (including auto-generator script).
>
> signal.h:
> - the "include" files can't contain conditional code (_WORDSIZE),
> move signal.h to system specific directories (or add an #include
> <arch_signal.h>)
> stat.h:
> - __pad0, __st_ino, etc. where did those come from ?
> - can't have __attribute__ extension in "include" directory (where
>  did those come from ?)
> - sigval_t this doesn't exist in the standard
>
> Are you copying this from an older implementation ? There are too many
> unexpected features in this patch. I need to understand what's this
> all about before I continue reading the patches. I can't spend time
> verifying that non standard code is being submitted, this has to be
> done by the contributor.
>
> 2009/6/12 Henrique Almeida <hd...@gm...>:
>>  Comments for commit:
>>
>>  9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build.
>>
>>  - uncomment #ifdef in syscall_nums.h
>>  - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi
>>
>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>  Broken branch updated up to 2009-06-05
>>>
>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>  Comments for commit:
>>>>
>>>>  3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr()
>>>> including unit tests.
>>>>
>>>>  on strrchr.c, '\0' must be considered part of the string, fix both
>>>> the implementation and test
>>>>
>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>  Comments for commit:
>>>>>
>>>>>  d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already
>>>>> implemented str* functions.
>>>>>
>>>>>  - remove test prefix from file names
>>>>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is
>>>>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13
>>>>> - add test coverage to strcmp: range 0, UCHAR_MAX
>>>>> - add test coverage to strcpy: out of bound writes (both sides)
>>>>>
>>>>>
>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>  Comments for commit:
>>>>>>
>>>>>>  1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap.
>>>>>>
>>>>>> - sys/mman.h
>>>>>>  - the PROT_* macros are system dependent (they depend on the kernel used).
>>>>>>   mman.h should be moved to the system directory. Also, the reference for
>>>>>>   the values for linux are missing.
>>>>>>
>>>>>>
>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>
>>>>>>>  I have done a git pull here and there are individual commits. I think I
>>>>>>> haven't noticed them earlier. I'll begin to read each of them.
>>>>>>>
>>>>>>> 2009/6/8 Henrique Almeida <hd...@gm...>
>>>>>>>>
>>>>>>>>  The problem was that the merge was condensed into a single commit (or
>>>>>>>> maybe I didn't notice the other commits in the log). I can try again later,
>>>>>>>> but at the moment there are some merge issues to resolve.
>>>>>>>>
>>>>>>>> 2009/6/8 Andreas Krennmair <akr...@go...>
>>>>>>>>>
>>>>>>>>> If there are differences, you always need an extra merge commit, as far
>>>>>>>>> as I understand.
>>>>>>>>>
>>>>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>  With git pull, I'm not being able to merge each commit individually in
>>>>>>>>>> my branch:
>>>>>>>>>>
>>>>>>>>>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>>>>>>>>>> Merge: 1faac1a... 05b56ea...
>>>>>>>>>> Author: Henrique <hd...@us...>
>>>>>>>>>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>>>>>>>>>
>>>>>>>>>>     Merge git://github.com/akrennmair/libposix into andreas
>>>>>>>>>>
>>>>>>>>>>     * git://github.com/akrennmair/libposix:
>>>>>>>>>>       implemented abs(), labs() and llabs() including unit tests.
>>>>>>>>>>       implemented strrchr() including unit tests.
>>>>>>>>>>       fixed build dependencies for tests.
>>>>>>>>>>       added unit tests for already implemented str* functions.
>>>>>>>>>>       added mmap and munmap.
>>>>>>>>>>       added simple unit tests for already implemented mem* functions.
>>>>>>>>>>
>>>>>>>>>>  Is there a way to fix this ?
>>>>>>>>>>
>>>>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>>>>>>>>>>
>>>>>>>>>>>  Ok, good idea, git branches rock !
>>>>>>>>>>>
>>>>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>>>>>>>>>>
>>>>>>>>>>>> Hello everybody,
>>>>>>>>>>>>
>>>>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better
>>>>>>>>>>>> way that both satisfies me in its abilities and also allows other developers
>>>>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on
>>>>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>>>>>>>>>> In this fork, I will regularly keep track of changes in the official
>>>>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the
>>>>>>>>>>>> official libposix repository by executing
>>>>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master
>>>>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be
>>>>>>>>>>>> interpreted as a way to get independent from the official project, it is
>>>>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things
>>>>>>>>>>>> that I want to work on, plus it makes my changes more visible and also
>>>>>>>>>>>> easier to reintegrate with the official development line.
>>>>>>>>>>>>
>>>>>>>>>>>> Nevertheless, I will continue posting short notifications about the
>>>>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>>>>>>>>>> some simple functions including unit tests, and I hope to present a simple
>>>>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>>>>>>>>>> two.
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Andreas
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>>>>> latest
>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>>> Lib...@li...
>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>> hd...@gm...
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>> hd...@gm...
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>>> latest
>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>> Lib...@li...
>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>> looking to deploy the next generation of Solaris that includes the latest
>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>> _______________________________________________
>>>>>>>>> Libposix-development mailing list
>>>>>>>>> Lib...@li...
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Henrique Dante de Almeida
>>>>>>>> hd...@gm...
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Henrique Dante de Almeida
>>>>>>> hd...@gm...
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>  Henrique Dante de Almeida
>>>>>>  hd...@gm...
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>  Henrique Dante de Almeida
>>>>>  hd...@gm...
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>  Henrique Dante de Almeida
>>>>  hd...@gm...
>>>>
>>>
>>>
>>>
>>> --
>>>  Henrique Dante de Almeida
>>>  hd...@gm...
>>>
>>
>>
>>
>> --
>>  Henrique Dante de Almeida
>>  hd...@gm...
>>
>
>
>
> --
>  Henrique Dante de Almeida
>  hd...@gm...
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>

Re: [libposix-development] My personal development branch

[Henrique A. <hd...@gm...>]

 No, that won't do. Submitted code must follow the standard (or must
go to system specific directories). It doesn't make sense for the
project otherwise.

 - Code that is contributed must be written for the standard. Linux is
not a standard. (for example, sigval_t is not defined in the standard,
sigval is, __band_t is not defined either).
 - System specific code that must go to the system directory. They
always need a reference that proves that they're necessary.
 - Code that is copied from other libraries must have original
author's notice, so that it can be tagged as derived work (and the
license must allow that).

2009/6/13 Andreas Krennmair <akr...@go...>:
> Henrique,
>
> I'm not pulling the struct definition out of my a**, Linux is the way
> it is (especially its kernel data structures), and there's nothing
> that can be changed about it from my side. If this is unacceptable,
> well, then I can't help you. Take the code or leave it, it's all your
> decision. Having to vindicate every single line of code that I
> contribute isn't exactly something that makes me eager to contribute
> more code.
>
> Best regards,
> Andreas
>
> On Sat, Jun 13, 2009 at 5:21 AM, Henrique Almeida<hd...@gm...> wrote:
>>  Comments for commit:
>>
>> 1e39bb5359952c6c6e28cc74f6651c98c8d86905 added auto-generated system
>> calls (including auto-generator script).
>>
>> signal.h:
>> - the "include" files can't contain conditional code (_WORDSIZE),
>> move signal.h to system specific directories (or add an #include
>> <arch_signal.h>)
>> stat.h:
>> - __pad0, __st_ino, etc. where did those come from ?
>> - can't have __attribute__ extension in "include" directory (where
>>  did those come from ?)
>> - sigval_t this doesn't exist in the standard
>>
>> Are you copying this from an older implementation ? There are too many
>> unexpected features in this patch. I need to understand what's this
>> all about before I continue reading the patches. I can't spend time
>> verifying that non standard code is being submitted, this has to be
>> done by the contributor.
>>
>> 2009/6/12 Henrique Almeida <hd...@gm...>:
>>>  Comments for commit:
>>>
>>>  9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build.
>>>
>>>  - uncomment #ifdef in syscall_nums.h
>>>  - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi
>>>
>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>  Broken branch updated up to 2009-06-05
>>>>
>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>  Comments for commit:
>>>>>
>>>>>  3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr()
>>>>> including unit tests.
>>>>>
>>>>>  on strrchr.c, '\0' must be considered part of the string, fix both
>>>>> the implementation and test
>>>>>
>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>  Comments for commit:
>>>>>>
>>>>>>  d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already
>>>>>> implemented str* functions.
>>>>>>
>>>>>>  - remove test prefix from file names
>>>>>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is
>>>>>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13
>>>>>> - add test coverage to strcmp: range 0, UCHAR_MAX
>>>>>> - add test coverage to strcpy: out of bound writes (both sides)
>>>>>>
>>>>>>
>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>  Comments for commit:
>>>>>>>
>>>>>>>  1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap.
>>>>>>>
>>>>>>> - sys/mman.h
>>>>>>>  - the PROT_* macros are system dependent (they depend on the kernel used).
>>>>>>>   mman.h should be moved to the system directory. Also, the reference for
>>>>>>>   the values for linux are missing.
>>>>>>>
>>>>>>>
>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>>
>>>>>>>>  I have done a git pull here and there are individual commits. I think I
>>>>>>>> haven't noticed them earlier. I'll begin to read each of them.
>>>>>>>>
>>>>>>>> 2009/6/8 Henrique Almeida <hd...@gm...>
>>>>>>>>>
>>>>>>>>>  The problem was that the merge was condensed into a single commit (or
>>>>>>>>> maybe I didn't notice the other commits in the log). I can try again later,
>>>>>>>>> but at the moment there are some merge issues to resolve.
>>>>>>>>>
>>>>>>>>> 2009/6/8 Andreas Krennmair <akr...@go...>
>>>>>>>>>>
>>>>>>>>>> If there are differences, you always need an extra merge commit, as far
>>>>>>>>>> as I understand.
>>>>>>>>>>
>>>>>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>  With git pull, I'm not being able to merge each commit individually in
>>>>>>>>>>> my branch:
>>>>>>>>>>>
>>>>>>>>>>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>>>>>>>>>>> Merge: 1faac1a... 05b56ea...
>>>>>>>>>>> Author: Henrique <hd...@us...>
>>>>>>>>>>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>>>>>>>>>>
>>>>>>>>>>>     Merge git://github.com/akrennmair/libposix into andreas
>>>>>>>>>>>
>>>>>>>>>>>     * git://github.com/akrennmair/libposix:
>>>>>>>>>>>       implemented abs(), labs() and llabs() including unit tests.
>>>>>>>>>>>       implemented strrchr() including unit tests.
>>>>>>>>>>>       fixed build dependencies for tests.
>>>>>>>>>>>       added unit tests for already implemented str* functions.
>>>>>>>>>>>       added mmap and munmap.
>>>>>>>>>>>       added simple unit tests for already implemented mem* functions.
>>>>>>>>>>>
>>>>>>>>>>>  Is there a way to fix this ?
>>>>>>>>>>>
>>>>>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>>>>>>>>>>>
>>>>>>>>>>>>  Ok, good idea, git branches rock !
>>>>>>>>>>>>
>>>>>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hello everybody,
>>>>>>>>>>>>>
>>>>>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better
>>>>>>>>>>>>> way that both satisfies me in its abilities and also allows other developers
>>>>>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on
>>>>>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>>>>>>>>>>> In this fork, I will regularly keep track of changes in the official
>>>>>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the
>>>>>>>>>>>>> official libposix repository by executing
>>>>>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master
>>>>>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>>>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be
>>>>>>>>>>>>> interpreted as a way to get independent from the official project, it is
>>>>>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things
>>>>>>>>>>>>> that I want to work on, plus it makes my changes more visible and also
>>>>>>>>>>>>> easier to reintegrate with the official development line.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Nevertheless, I will continue posting short notifications about the
>>>>>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>>>>>>>>>>> some simple functions including unit tests, and I hope to present a simple
>>>>>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>>>>>>>>>>> two.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Andreas
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>>>>>> latest
>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>>>> Lib...@li...
>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>>> hd...@gm...
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>> hd...@gm...
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>>>> latest
>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>> Lib...@li...
>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>> looking to deploy the next generation of Solaris that includes the latest
>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>> Lib...@li...
>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>> hd...@gm...
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Henrique Dante de Almeida
>>>>>>>> hd...@gm...
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>  Henrique Dante de Almeida
>>>>>>>  hd...@gm...
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>  Henrique Dante de Almeida
>>>>>>  hd...@gm...
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>  Henrique Dante de Almeida
>>>>>  hd...@gm...
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>  Henrique Dante de Almeida
>>>>  hd...@gm...
>>>>
>>>
>>>
>>>
>>> --
>>>  Henrique Dante de Almeida
>>>  hd...@gm...
>>>
>>
>>
>>
>> --
>>  Henrique Dante de Almeida
>>  hd...@gm...
>>
>> ------------------------------------------------------------------------------
>> Crystal Reports - New Free Runtime and 30 Day Trial
>> Check out the new simplified licensing option that enables unlimited
>> royalty-free distribution of the report engine for externally facing
>> server and web deployment.
>> http://p.sf.net/sfu/businessobjects
>> _______________________________________________
>> Libposix-development mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>



-- 
 Henrique Dante de Almeida
 hd...@gm...

Re: [libposix-development] My personal development branch

[Andreas K. <akr...@go...>]

Linux is not a standard, but Linux is real! If you want to support
certain system calls on Linux, you must adhere to Linux's data
structures. Or are you trying to suggest that I should write a wrapper
around such things that map the Linux data structures to data
structures that adhere to POSIX.1-2008 and POSIX.1-2008 only? That
would be just outright crazy.

Anyway, your tight restrictions on the code and all your fighting
about the confrontation with real-world conditions really took my last
motivation to contribute my code. Apparently, working on the code
itself for this project is fun, and I will keep developing in my own
development branch, but don't expect me to report any improvements or
changes that I made here.

Good luck to you and all the other contributing C developers, low
level developers, testers, web designers, web developers, web
editors/bloggers/"PR guys", build system developers/port maintainers,
performance developers, roadmap managers and code reviewers. With more
stringent code conformity rules and tighter project roles, you will
surely make it!

Best regards,
Andreas

On Sat, Jun 13, 2009 at 11:14 PM, Henrique Almeida<hd...@gm...> wrote:
>  No, that won't do. Submitted code must follow the standard (or must
> go to system specific directories). It doesn't make sense for the
> project otherwise.
>
>  - Code that is contributed must be written for the standard. Linux is
> not a standard. (for example, sigval_t is not defined in the standard,
> sigval is, __band_t is not defined either).
>  - System specific code that must go to the system directory. They
> always need a reference that proves that they're necessary.
>  - Code that is copied from other libraries must have original
> author's notice, so that it can be tagged as derived work (and the
> license must allow that).
>
> 2009/6/13 Andreas Krennmair <akr...@go...>:
>> Henrique,
>>
>> I'm not pulling the struct definition out of my a**, Linux is the way
>> it is (especially its kernel data structures), and there's nothing
>> that can be changed about it from my side. If this is unacceptable,
>> well, then I can't help you. Take the code or leave it, it's all your
>> decision. Having to vindicate every single line of code that I
>> contribute isn't exactly something that makes me eager to contribute
>> more code.
>>
>> Best regards,
>> Andreas
>>
>> On Sat, Jun 13, 2009 at 5:21 AM, Henrique Almeida<hd...@gm...> wrote:
>>>  Comments for commit:
>>>
>>> 1e39bb5359952c6c6e28cc74f6651c98c8d86905 added auto-generated system
>>> calls (including auto-generator script).
>>>
>>> signal.h:
>>> - the "include" files can't contain conditional code (_WORDSIZE),
>>> move signal.h to system specific directories (or add an #include
>>> <arch_signal.h>)
>>> stat.h:
>>> - __pad0, __st_ino, etc. where did those come from ?
>>> - can't have __attribute__ extension in "include" directory (where
>>>  did those come from ?)
>>> - sigval_t this doesn't exist in the standard
>>>
>>> Are you copying this from an older implementation ? There are too many
>>> unexpected features in this patch. I need to understand what's this
>>> all about before I continue reading the patches. I can't spend time
>>> verifying that non standard code is being submitted, this has to be
>>> done by the contributor.
>>>
>>> 2009/6/12 Henrique Almeida <hd...@gm...>:
>>>>  Comments for commit:
>>>>
>>>>  9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build.
>>>>
>>>>  - uncomment #ifdef in syscall_nums.h
>>>>  - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi
>>>>
>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>  Broken branch updated up to 2009-06-05
>>>>>
>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>  Comments for commit:
>>>>>>
>>>>>>  3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr()
>>>>>> including unit tests.
>>>>>>
>>>>>>  on strrchr.c, '\0' must be considered part of the string, fix both
>>>>>> the implementation and test
>>>>>>
>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>  Comments for commit:
>>>>>>>
>>>>>>>  d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already
>>>>>>> implemented str* functions.
>>>>>>>
>>>>>>>  - remove test prefix from file names
>>>>>>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is
>>>>>>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13
>>>>>>> - add test coverage to strcmp: range 0, UCHAR_MAX
>>>>>>> - add test coverage to strcpy: out of bound writes (both sides)
>>>>>>>
>>>>>>>
>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>>  Comments for commit:
>>>>>>>>
>>>>>>>>  1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap.
>>>>>>>>
>>>>>>>> - sys/mman.h
>>>>>>>>  - the PROT_* macros are system dependent (they depend on the kernel used).
>>>>>>>>   mman.h should be moved to the system directory. Also, the reference for
>>>>>>>>   the values for linux are missing.
>>>>>>>>
>>>>>>>>
>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>>>
>>>>>>>>>  I have done a git pull here and there are individual commits. I think I
>>>>>>>>> haven't noticed them earlier. I'll begin to read each of them.
>>>>>>>>>
>>>>>>>>> 2009/6/8 Henrique Almeida <hd...@gm...>
>>>>>>>>>>
>>>>>>>>>>  The problem was that the merge was condensed into a single commit (or
>>>>>>>>>> maybe I didn't notice the other commits in the log). I can try again later,
>>>>>>>>>> but at the moment there are some merge issues to resolve.
>>>>>>>>>>
>>>>>>>>>> 2009/6/8 Andreas Krennmair <akr...@go...>
>>>>>>>>>>>
>>>>>>>>>>> If there are differences, you always need an extra merge commit, as far
>>>>>>>>>>> as I understand.
>>>>>>>>>>>
>>>>>>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>  With git pull, I'm not being able to merge each commit individually in
>>>>>>>>>>>> my branch:
>>>>>>>>>>>>
>>>>>>>>>>>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>>>>>>>>>>>> Merge: 1faac1a... 05b56ea...
>>>>>>>>>>>> Author: Henrique <hd...@us...>
>>>>>>>>>>>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>>>>>>>>>>>
>>>>>>>>>>>>     Merge git://github.com/akrennmair/libposix into andreas
>>>>>>>>>>>>
>>>>>>>>>>>>     * git://github.com/akrennmair/libposix:
>>>>>>>>>>>>       implemented abs(), labs() and llabs() including unit tests.
>>>>>>>>>>>>       implemented strrchr() including unit tests.
>>>>>>>>>>>>       fixed build dependencies for tests.
>>>>>>>>>>>>       added unit tests for already implemented str* functions.
>>>>>>>>>>>>       added mmap and munmap.
>>>>>>>>>>>>       added simple unit tests for already implemented mem* functions.
>>>>>>>>>>>>
>>>>>>>>>>>>  Is there a way to fix this ?
>>>>>>>>>>>>
>>>>>>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>>>>>>>>>>>>
>>>>>>>>>>>>>  Ok, good idea, git branches rock !
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hello everybody,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better
>>>>>>>>>>>>>> way that both satisfies me in its abilities and also allows other developers
>>>>>>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on
>>>>>>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>>>>>>>>>>>> In this fork, I will regularly keep track of changes in the official
>>>>>>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the
>>>>>>>>>>>>>> official libposix repository by executing
>>>>>>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master
>>>>>>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>>>>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be
>>>>>>>>>>>>>> interpreted as a way to get independent from the official project, it is
>>>>>>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things
>>>>>>>>>>>>>> that I want to work on, plus it makes my changes more visible and also
>>>>>>>>>>>>>> easier to reintegrate with the official development line.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Nevertheless, I will continue posting short notifications about the
>>>>>>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>>>>>>>>>>>> some simple functions including unit tests, and I hope to present a simple
>>>>>>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>>>>>>>>>>>> two.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>> Andreas
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>>>>>>> latest
>>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>>>>> Lib...@li...
>>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>>>> hd...@gm...
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>>> hd...@gm...
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>>>>> latest
>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>>> Lib...@li...
>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the latest
>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>> Lib...@li...
>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>> hd...@gm...
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>> hd...@gm...
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>  Henrique Dante de Almeida
>>>>>>>>  hd...@gm...
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>  Henrique Dante de Almeida
>>>>>>>  hd...@gm...
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>  Henrique Dante de Almeida
>>>>>>  hd...@gm...
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>  Henrique Dante de Almeida
>>>>>  hd...@gm...
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>  Henrique Dante de Almeida
>>>>  hd...@gm...
>>>>
>>>
>>>
>>>
>>> --
>>>  Henrique Dante de Almeida
>>>  hd...@gm...
>>>
>>> ------------------------------------------------------------------------------
>>> Crystal Reports - New Free Runtime and 30 Day Trial
>>> Check out the new simplified licensing option that enables unlimited
>>> royalty-free distribution of the report engine for externally facing
>>> server and web deployment.
>>> http://p.sf.net/sfu/businessobjects
>>> _______________________________________________
>>> Libposix-development mailing list
>>> Lib...@li...
>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>
>>
>> ------------------------------------------------------------------------------
>> Crystal Reports - New Free Runtime and 30 Day Trial
>> Check out the new simplified licensing option that enables unlimited
>> royalty-free distribution of the report engine for externally facing
>> server and web deployment.
>> http://p.sf.net/sfu/businessobjects
>> _______________________________________________
>> Libposix-development mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>
>
>
>
> --
>  Henrique Dante de Almeida
>  hd...@gm...
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>

Re: [libposix-development] My personal development branch

[Henrique A. <hd...@gm...>]

 I don't think the code rules are overly stringent. The method to deal
with real world implementations was described in the last post (so I
don't need to repeat it here). I don't think organizing things is
ridiculous either. Actually, I'm very proud of doing that way.

 See you,

2009/6/14 Andreas Krennmair <akr...@go...>:
> Linux is not a standard, but Linux is real! If you want to support
> certain system calls on Linux, you must adhere to Linux's data
> structures. Or are you trying to suggest that I should write a wrapper
> around such things that map the Linux data structures to data
> structures that adhere to POSIX.1-2008 and POSIX.1-2008 only? That
> would be just outright crazy.
>
> Anyway, your tight restrictions on the code and all your fighting
> about the confrontation with real-world conditions really took my last
> motivation to contribute my code. Apparently, working on the code
> itself for this project is fun, and I will keep developing in my own
> development branch, but don't expect me to report any improvements or
> changes that I made here.
>
> Good luck to you and all the other contributing C developers, low
> level developers, testers, web designers, web developers, web
> editors/bloggers/"PR guys", build system developers/port maintainers,
> performance developers, roadmap managers and code reviewers. With more
> stringent code conformity rules and tighter project roles, you will
> surely make it!
>
> Best regards,
> Andreas
>
> On Sat, Jun 13, 2009 at 11:14 PM, Henrique Almeida<hd...@gm...> wrote:
>>  No, that won't do. Submitted code must follow the standard (or must
>> go to system specific directories). It doesn't make sense for the
>> project otherwise.
>>
>>  - Code that is contributed must be written for the standard. Linux is
>> not a standard. (for example, sigval_t is not defined in the standard,
>> sigval is, __band_t is not defined either).
>>  - System specific code that must go to the system directory. They
>> always need a reference that proves that they're necessary.
>>  - Code that is copied from other libraries must have original
>> author's notice, so that it can be tagged as derived work (and the
>> license must allow that).
>>
>> 2009/6/13 Andreas Krennmair <akr...@go...>:
>>> Henrique,
>>>
>>> I'm not pulling the struct definition out of my a**, Linux is the way
>>> it is (especially its kernel data structures), and there's nothing
>>> that can be changed about it from my side. If this is unacceptable,
>>> well, then I can't help you. Take the code or leave it, it's all your
>>> decision. Having to vindicate every single line of code that I
>>> contribute isn't exactly something that makes me eager to contribute
>>> more code.
>>>
>>> Best regards,
>>> Andreas
>>>
>>> On Sat, Jun 13, 2009 at 5:21 AM, Henrique Almeida<hd...@gm...> wrote:
>>>>  Comments for commit:
>>>>
>>>> 1e39bb5359952c6c6e28cc74f6651c98c8d86905 added auto-generated system
>>>> calls (including auto-generator script).
>>>>
>>>> signal.h:
>>>> - the "include" files can't contain conditional code (_WORDSIZE),
>>>> move signal.h to system specific directories (or add an #include
>>>> <arch_signal.h>)
>>>> stat.h:
>>>> - __pad0, __st_ino, etc. where did those come from ?
>>>> - can't have __attribute__ extension in "include" directory (where
>>>>  did those come from ?)
>>>> - sigval_t this doesn't exist in the standard
>>>>
>>>> Are you copying this from an older implementation ? There are too many
>>>> unexpected features in this patch. I need to understand what's this
>>>> all about before I continue reading the patches. I can't spend time
>>>> verifying that non standard code is being submitted, this has to be
>>>> done by the contributor.
>>>>
>>>> 2009/6/12 Henrique Almeida <hd...@gm...>:
>>>>>  Comments for commit:
>>>>>
>>>>>  9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build.
>>>>>
>>>>>  - uncomment #ifdef in syscall_nums.h
>>>>>  - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi
>>>>>
>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>  Broken branch updated up to 2009-06-05
>>>>>>
>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>  Comments for commit:
>>>>>>>
>>>>>>>  3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr()
>>>>>>> including unit tests.
>>>>>>>
>>>>>>>  on strrchr.c, '\0' must be considered part of the string, fix both
>>>>>>> the implementation and test
>>>>>>>
>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>>  Comments for commit:
>>>>>>>>
>>>>>>>>  d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already
>>>>>>>> implemented str* functions.
>>>>>>>>
>>>>>>>>  - remove test prefix from file names
>>>>>>>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is
>>>>>>>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13
>>>>>>>> - add test coverage to strcmp: range 0, UCHAR_MAX
>>>>>>>> - add test coverage to strcpy: out of bound writes (both sides)
>>>>>>>>
>>>>>>>>
>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>>>  Comments for commit:
>>>>>>>>>
>>>>>>>>>  1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap.
>>>>>>>>>
>>>>>>>>> - sys/mman.h
>>>>>>>>>  - the PROT_* macros are system dependent (they depend on the kernel used).
>>>>>>>>>   mman.h should be moved to the system directory. Also, the reference for
>>>>>>>>>   the values for linux are missing.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>>>>
>>>>>>>>>>  I have done a git pull here and there are individual commits. I think I
>>>>>>>>>> haven't noticed them earlier. I'll begin to read each of them.
>>>>>>>>>>
>>>>>>>>>> 2009/6/8 Henrique Almeida <hd...@gm...>
>>>>>>>>>>>
>>>>>>>>>>>  The problem was that the merge was condensed into a single commit (or
>>>>>>>>>>> maybe I didn't notice the other commits in the log). I can try again later,
>>>>>>>>>>> but at the moment there are some merge issues to resolve.
>>>>>>>>>>>
>>>>>>>>>>> 2009/6/8 Andreas Krennmair <akr...@go...>
>>>>>>>>>>>>
>>>>>>>>>>>> If there are differences, you always need an extra merge commit, as far
>>>>>>>>>>>> as I understand.
>>>>>>>>>>>>
>>>>>>>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>  With git pull, I'm not being able to merge each commit individually in
>>>>>>>>>>>>> my branch:
>>>>>>>>>>>>>
>>>>>>>>>>>>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>>>>>>>>>>>>> Merge: 1faac1a... 05b56ea...
>>>>>>>>>>>>> Author: Henrique <hd...@us...>
>>>>>>>>>>>>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>>>>>>>>>>>>
>>>>>>>>>>>>>     Merge git://github.com/akrennmair/libposix into andreas
>>>>>>>>>>>>>
>>>>>>>>>>>>>     * git://github.com/akrennmair/libposix:
>>>>>>>>>>>>>       implemented abs(), labs() and llabs() including unit tests.
>>>>>>>>>>>>>       implemented strrchr() including unit tests.
>>>>>>>>>>>>>       fixed build dependencies for tests.
>>>>>>>>>>>>>       added unit tests for already implemented str* functions.
>>>>>>>>>>>>>       added mmap and munmap.
>>>>>>>>>>>>>       added simple unit tests for already implemented mem* functions.
>>>>>>>>>>>>>
>>>>>>>>>>>>>  Is there a way to fix this ?
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>  Ok, good idea, git branches rock !
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hello everybody,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better
>>>>>>>>>>>>>>> way that both satisfies me in its abilities and also allows other developers
>>>>>>>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on
>>>>>>>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>>>>>>>>>>>>> In this fork, I will regularly keep track of changes in the official
>>>>>>>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the
>>>>>>>>>>>>>>> official libposix repository by executing
>>>>>>>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master
>>>>>>>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>>>>>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be
>>>>>>>>>>>>>>> interpreted as a way to get independent from the official project, it is
>>>>>>>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things
>>>>>>>>>>>>>>> that I want to work on, plus it makes my changes more visible and also
>>>>>>>>>>>>>>> easier to reintegrate with the official development line.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Nevertheless, I will continue posting short notifications about the
>>>>>>>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>>>>>>>>>>>>> some simple functions including unit tests, and I hope to present a simple
>>>>>>>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>>>>>>>>>>>>> two.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>> Andreas
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>>>>>>>> latest
>>>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>>>>>> Lib...@li...
>>>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>>>>> hd...@gm...
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>>>> hd...@gm...
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>>>>>> latest
>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>>>> Lib...@li...
>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the latest
>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>>> Lib...@li...
>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>> hd...@gm...
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>> hd...@gm...
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>  Henrique Dante de Almeida
>>>>>>>>>  hd...@gm...
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>  Henrique Dante de Almeida
>>>>>>>>  hd...@gm...
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>  Henrique Dante de Almeida
>>>>>>>  hd...@gm...
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>  Henrique Dante de Almeida
>>>>>>  hd...@gm...
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>  Henrique Dante de Almeida
>>>>>  hd...@gm...
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>  Henrique Dante de Almeida
>>>>  hd...@gm...
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Crystal Reports - New Free Runtime and 30 Day Trial
>>>> Check out the new simplified licensing option that enables unlimited
>>>> royalty-free distribution of the report engine for externally facing
>>>> server and web deployment.
>>>> http://p.sf.net/sfu/businessobjects
>>>> _______________________________________________
>>>> Libposix-development mailing list
>>>> Lib...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Crystal Reports - New Free Runtime and 30 Day Trial
>>> Check out the new simplified licensing option that enables unlimited
>>> royalty-free distribution of the report engine for externally facing
>>> server and web deployment.
>>> http://p.sf.net/sfu/businessobjects
>>> _______________________________________________
>>> Libposix-development mailing list
>>> Lib...@li...
>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>
>>
>>
>>
>> --
>>  Henrique Dante de Almeida
>>  hd...@gm...
>>
>> ------------------------------------------------------------------------------
>> Crystal Reports - New Free Runtime and 30 Day Trial
>> Check out the new simplified licensing option that enables unlimited
>> royalty-free distribution of the report engine for externally facing
>> server and web deployment.
>> http://p.sf.net/sfu/businessobjects
>> _______________________________________________
>> Libposix-development mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>



-- 
 Henrique Dante de Almeida
 hd...@gm...

Re: [libposix-development] My personal development branch

[Andreas K. <akr...@go...>]

Henrique,

Open source projects simply don't work that way. You attacked me for
not immediately implementing the rules of architecture independence.
Why can't you simply fix that when merging the commits? As I already
wrote, my changes are x86_64 specific, as this is pretty much the only
platform that I have available.

In the case of libposix, you have the real world (Linux) and the
standard world (POSIX.1-2008). Both world differ, but in order to
implement the standard, you need to interconnect with the real world,
and you cannot completely ignore it. Finding a practical way to
interconnect these two worlds is not something that can be planned
easily, and there will be changes to it, at least once more than
planned. And you require me to "get it right" up-front?! That's just
ridiculous. Software development has a tool to remedy such problems,
it is called "refactoring". You're going to need it in the future,
even with your strict separation of "master" and "broken" branches.

Having said that, I think that you, taking pride in your up-front
planning efforts without any practical need (how many other developers
contribute code, too?), have no clue how open source projects are
managed and why people take part in open source projects. It's not my
job to work on libposix, I purely do this for fun and joy, and having
to obey to all the rules that you make up in order to organize things
(organize what? who? there is practically nothing and nobody that
needs to be managed and/or organized yet!) really takes away the fun
from the project, the very essence of why I have contributed so far.

Regards,
Andreas

On Sun, Jun 14, 2009 at 8:08 PM, Henrique Almeida<hd...@gm...> wrote:
>  I don't think the code rules are overly stringent. The method to deal
> with real world implementations was described in the last post (so I
> don't need to repeat it here). I don't think organizing things is
> ridiculous either. Actually, I'm very proud of doing that way.
>
>  See you,
>
> 2009/6/14 Andreas Krennmair <akr...@go...>:
>> Linux is not a standard, but Linux is real! If you want to support
>> certain system calls on Linux, you must adhere to Linux's data
>> structures. Or are you trying to suggest that I should write a wrapper
>> around such things that map the Linux data structures to data
>> structures that adhere to POSIX.1-2008 and POSIX.1-2008 only? That
>> would be just outright crazy.
>>
>> Anyway, your tight restrictions on the code and all your fighting
>> about the confrontation with real-world conditions really took my last
>> motivation to contribute my code. Apparently, working on the code
>> itself for this project is fun, and I will keep developing in my own
>> development branch, but don't expect me to report any improvements or
>> changes that I made here.
>>
>> Good luck to you and all the other contributing C developers, low
>> level developers, testers, web designers, web developers, web
>> editors/bloggers/"PR guys", build system developers/port maintainers,
>> performance developers, roadmap managers and code reviewers. With more
>> stringent code conformity rules and tighter project roles, you will
>> surely make it!
>>
>> Best regards,
>> Andreas
>>
>> On Sat, Jun 13, 2009 at 11:14 PM, Henrique Almeida<hd...@gm...> wrote:
>>>  No, that won't do. Submitted code must follow the standard (or must
>>> go to system specific directories). It doesn't make sense for the
>>> project otherwise.
>>>
>>>  - Code that is contributed must be written for the standard. Linux is
>>> not a standard. (for example, sigval_t is not defined in the standard,
>>> sigval is, __band_t is not defined either).
>>>  - System specific code that must go to the system directory. They
>>> always need a reference that proves that they're necessary.
>>>  - Code that is copied from other libraries must have original
>>> author's notice, so that it can be tagged as derived work (and the
>>> license must allow that).
>>>
>>> 2009/6/13 Andreas Krennmair <akr...@go...>:
>>>> Henrique,
>>>>
>>>> I'm not pulling the struct definition out of my a**, Linux is the way
>>>> it is (especially its kernel data structures), and there's nothing
>>>> that can be changed about it from my side. If this is unacceptable,
>>>> well, then I can't help you. Take the code or leave it, it's all your
>>>> decision. Having to vindicate every single line of code that I
>>>> contribute isn't exactly something that makes me eager to contribute
>>>> more code.
>>>>
>>>> Best regards,
>>>> Andreas
>>>>
>>>> On Sat, Jun 13, 2009 at 5:21 AM, Henrique Almeida<hd...@gm...> wrote:
>>>>>  Comments for commit:
>>>>>
>>>>> 1e39bb5359952c6c6e28cc74f6651c98c8d86905 added auto-generated system
>>>>> calls (including auto-generator script).
>>>>>
>>>>> signal.h:
>>>>> - the "include" files can't contain conditional code (_WORDSIZE),
>>>>> move signal.h to system specific directories (or add an #include
>>>>> <arch_signal.h>)
>>>>> stat.h:
>>>>> - __pad0, __st_ino, etc. where did those come from ?
>>>>> - can't have __attribute__ extension in "include" directory (where
>>>>>  did those come from ?)
>>>>> - sigval_t this doesn't exist in the standard
>>>>>
>>>>> Are you copying this from an older implementation ? There are too many
>>>>> unexpected features in this patch. I need to understand what's this
>>>>> all about before I continue reading the patches. I can't spend time
>>>>> verifying that non standard code is being submitted, this has to be
>>>>> done by the contributor.
>>>>>
>>>>> 2009/6/12 Henrique Almeida <hd...@gm...>:
>>>>>>  Comments for commit:
>>>>>>
>>>>>>  9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build.
>>>>>>
>>>>>>  - uncomment #ifdef in syscall_nums.h
>>>>>>  - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi
>>>>>>
>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>  Broken branch updated up to 2009-06-05
>>>>>>>
>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>>  Comments for commit:
>>>>>>>>
>>>>>>>>  3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr()
>>>>>>>> including unit tests.
>>>>>>>>
>>>>>>>>  on strrchr.c, '\0' must be considered part of the string, fix both
>>>>>>>> the implementation and test
>>>>>>>>
>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>>>  Comments for commit:
>>>>>>>>>
>>>>>>>>>  d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already
>>>>>>>>> implemented str* functions.
>>>>>>>>>
>>>>>>>>>  - remove test prefix from file names
>>>>>>>>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is
>>>>>>>>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13
>>>>>>>>> - add test coverage to strcmp: range 0, UCHAR_MAX
>>>>>>>>> - add test coverage to strcpy: out of bound writes (both sides)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>>>>  Comments for commit:
>>>>>>>>>>
>>>>>>>>>>  1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap.
>>>>>>>>>>
>>>>>>>>>> - sys/mman.h
>>>>>>>>>>  - the PROT_* macros are system dependent (they depend on the kernel used).
>>>>>>>>>>   mman.h should be moved to the system directory. Also, the reference for
>>>>>>>>>>   the values for linux are missing.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>>>>>
>>>>>>>>>>>  I have done a git pull here and there are individual commits. I think I
>>>>>>>>>>> haven't noticed them earlier. I'll begin to read each of them.
>>>>>>>>>>>
>>>>>>>>>>> 2009/6/8 Henrique Almeida <hd...@gm...>
>>>>>>>>>>>>
>>>>>>>>>>>>  The problem was that the merge was condensed into a single commit (or
>>>>>>>>>>>> maybe I didn't notice the other commits in the log). I can try again later,
>>>>>>>>>>>> but at the moment there are some merge issues to resolve.
>>>>>>>>>>>>
>>>>>>>>>>>> 2009/6/8 Andreas Krennmair <akr...@go...>
>>>>>>>>>>>>>
>>>>>>>>>>>>> If there are differences, you always need an extra merge commit, as far
>>>>>>>>>>>>> as I understand.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>  With git pull, I'm not being able to merge each commit individually in
>>>>>>>>>>>>>> my branch:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>>>>>>>>>>>>>> Merge: 1faac1a... 05b56ea...
>>>>>>>>>>>>>> Author: Henrique <hd...@us...>
>>>>>>>>>>>>>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>     Merge git://github.com/akrennmair/libposix into andreas
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>     * git://github.com/akrennmair/libposix:
>>>>>>>>>>>>>>       implemented abs(), labs() and llabs() including unit tests.
>>>>>>>>>>>>>>       implemented strrchr() including unit tests.
>>>>>>>>>>>>>>       fixed build dependencies for tests.
>>>>>>>>>>>>>>       added unit tests for already implemented str* functions.
>>>>>>>>>>>>>>       added mmap and munmap.
>>>>>>>>>>>>>>       added simple unit tests for already implemented mem* functions.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>  Is there a way to fix this ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>  Ok, good idea, git branches rock !
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hello everybody,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better
>>>>>>>>>>>>>>>> way that both satisfies me in its abilities and also allows other developers
>>>>>>>>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on
>>>>>>>>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>>>>>>>>>>>>>> In this fork, I will regularly keep track of changes in the official
>>>>>>>>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the
>>>>>>>>>>>>>>>> official libposix repository by executing
>>>>>>>>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master
>>>>>>>>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>>>>>>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be
>>>>>>>>>>>>>>>> interpreted as a way to get independent from the official project, it is
>>>>>>>>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things
>>>>>>>>>>>>>>>> that I want to work on, plus it makes my changes more visible and also
>>>>>>>>>>>>>>>> easier to reintegrate with the official development line.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Nevertheless, I will continue posting short notifications about the
>>>>>>>>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>>>>>>>>>>>>>> some simple functions including unit tests, and I hope to present a simple
>>>>>>>>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>>>>>>>>>>>>>> two.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>> Andreas
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>>>>>>>>> latest
>>>>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>>>>>>> Lib...@li...
>>>>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>>>>>> hd...@gm...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>>>>> hd...@gm...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>>>>>>> latest
>>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>>>>> Lib...@li...
>>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the latest
>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>>>> Lib...@li...
>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>>> hd...@gm...
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>> hd...@gm...
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>  Henrique Dante de Almeida
>>>>>>>>>>  hd...@gm...
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>  Henrique Dante de Almeida
>>>>>>>>>  hd...@gm...
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>  Henrique Dante de Almeida
>>>>>>>>  hd...@gm...
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>  Henrique Dante de Almeida
>>>>>>>  hd...@gm...
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>  Henrique Dante de Almeida
>>>>>>  hd...@gm...
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>  Henrique Dante de Almeida
>>>>>  hd...@gm...
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Crystal Reports - New Free Runtime and 30 Day Trial
>>>>> Check out the new simplified licensing option that enables unlimited
>>>>> royalty-free distribution of the report engine for externally facing
>>>>> server and web deployment.
>>>>> http://p.sf.net/sfu/businessobjects
>>>>> _______________________________________________
>>>>> Libposix-development mailing list
>>>>> Lib...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Crystal Reports - New Free Runtime and 30 Day Trial
>>>> Check out the new simplified licensing option that enables unlimited
>>>> royalty-free distribution of the report engine for externally facing
>>>> server and web deployment.
>>>> http://p.sf.net/sfu/businessobjects
>>>> _______________________________________________
>>>> Libposix-development mailing list
>>>> Lib...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>
>>>
>>>
>>>
>>> --
>>>  Henrique Dante de Almeida
>>>  hd...@gm...
>>>
>>> ------------------------------------------------------------------------------
>>> Crystal Reports - New Free Runtime and 30 Day Trial
>>> Check out the new simplified licensing option that enables unlimited
>>> royalty-free distribution of the report engine for externally facing
>>> server and web deployment.
>>> http://p.sf.net/sfu/businessobjects
>>> _______________________________________________
>>> Libposix-development mailing list
>>> Lib...@li...
>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>
>>
>> ------------------------------------------------------------------------------
>> Crystal Reports - New Free Runtime and 30 Day Trial
>> Check out the new simplified licensing option that enables unlimited
>> royalty-free distribution of the report engine for externally facing
>> server and web deployment.
>> http://p.sf.net/sfu/businessobjects
>> _______________________________________________
>> Libposix-development mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>
>
>
>
> --
>  Henrique Dante de Almeida
>  hd...@gm...
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>

Re: [libposix-development] My personal development branch

[Henrique A. <hd...@gm...>]

 I'm not attacking anyone. And sorry, I won't keep arguing, specially
when someone starts assuming I've said things that I didn't. The
project will get it right, the sooner the better, but it doesn't
really matter when.

2009/6/14 Andreas Krennmair <akr...@go...>:
> Henrique,
>
> Open source projects simply don't work that way. You attacked me for
> not immediately implementing the rules of architecture independence.
> Why can't you simply fix that when merging the commits? As I already
> wrote, my changes are x86_64 specific, as this is pretty much the only
> platform that I have available.
>
> In the case of libposix, you have the real world (Linux) and the
> standard world (POSIX.1-2008). Both world differ, but in order to
> implement the standard, you need to interconnect with the real world,
> and you cannot completely ignore it. Finding a practical way to
> interconnect these two worlds is not something that can be planned
> easily, and there will be changes to it, at least once more than
> planned. And you require me to "get it right" up-front?! That's just
> ridiculous. Software development has a tool to remedy such problems,
> it is called "refactoring". You're going to need it in the future,
> even with your strict separation of "master" and "broken" branches.
>
> Having said that, I think that you, taking pride in your up-front
> planning efforts without any practical need (how many other developers
> contribute code, too?), have no clue how open source projects are
> managed and why people take part in open source projects. It's not my
> job to work on libposix, I purely do this for fun and joy, and having
> to obey to all the rules that you make up in order to organize things
> (organize what? who? there is practically nothing and nobody that
> needs to be managed and/or organized yet!) really takes away the fun
> from the project, the very essence of why I have contributed so far.
>
> Regards,
> Andreas
>
> On Sun, Jun 14, 2009 at 8:08 PM, Henrique Almeida<hd...@gm...> wrote:
>>  I don't think the code rules are overly stringent. The method to deal
>> with real world implementations was described in the last post (so I
>> don't need to repeat it here). I don't think organizing things is
>> ridiculous either. Actually, I'm very proud of doing that way.
>>
>>  See you,
>>
>> 2009/6/14 Andreas Krennmair <akr...@go...>:
>>> Linux is not a standard, but Linux is real! If you want to support
>>> certain system calls on Linux, you must adhere to Linux's data
>>> structures. Or are you trying to suggest that I should write a wrapper
>>> around such things that map the Linux data structures to data
>>> structures that adhere to POSIX.1-2008 and POSIX.1-2008 only? That
>>> would be just outright crazy.
>>>
>>> Anyway, your tight restrictions on the code and all your fighting
>>> about the confrontation with real-world conditions really took my last
>>> motivation to contribute my code. Apparently, working on the code
>>> itself for this project is fun, and I will keep developing in my own
>>> development branch, but don't expect me to report any improvements or
>>> changes that I made here.
>>>
>>> Good luck to you and all the other contributing C developers, low
>>> level developers, testers, web designers, web developers, web
>>> editors/bloggers/"PR guys", build system developers/port maintainers,
>>> performance developers, roadmap managers and code reviewers. With more
>>> stringent code conformity rules and tighter project roles, you will
>>> surely make it!
>>>
>>> Best regards,
>>> Andreas
>>>
>>> On Sat, Jun 13, 2009 at 11:14 PM, Henrique Almeida<hd...@gm...> wrote:
>>>>  No, that won't do. Submitted code must follow the standard (or must
>>>> go to system specific directories). It doesn't make sense for the
>>>> project otherwise.
>>>>
>>>>  - Code that is contributed must be written for the standard. Linux is
>>>> not a standard. (for example, sigval_t is not defined in the standard,
>>>> sigval is, __band_t is not defined either).
>>>>  - System specific code that must go to the system directory. They
>>>> always need a reference that proves that they're necessary.
>>>>  - Code that is copied from other libraries must have original
>>>> author's notice, so that it can be tagged as derived work (and the
>>>> license must allow that).
>>>>
>>>> 2009/6/13 Andreas Krennmair <akr...@go...>:
>>>>> Henrique,
>>>>>
>>>>> I'm not pulling the struct definition out of my a**, Linux is the way
>>>>> it is (especially its kernel data structures), and there's nothing
>>>>> that can be changed about it from my side. If this is unacceptable,
>>>>> well, then I can't help you. Take the code or leave it, it's all your
>>>>> decision. Having to vindicate every single line of code that I
>>>>> contribute isn't exactly something that makes me eager to contribute
>>>>> more code.
>>>>>
>>>>> Best regards,
>>>>> Andreas
>>>>>
>>>>> On Sat, Jun 13, 2009 at 5:21 AM, Henrique Almeida<hd...@gm...> wrote:
>>>>>>  Comments for commit:
>>>>>>
>>>>>> 1e39bb5359952c6c6e28cc74f6651c98c8d86905 added auto-generated system
>>>>>> calls (including auto-generator script).
>>>>>>
>>>>>> signal.h:
>>>>>> - the "include" files can't contain conditional code (_WORDSIZE),
>>>>>> move signal.h to system specific directories (or add an #include
>>>>>> <arch_signal.h>)
>>>>>> stat.h:
>>>>>> - __pad0, __st_ino, etc. where did those come from ?
>>>>>> - can't have __attribute__ extension in "include" directory (where
>>>>>>  did those come from ?)
>>>>>> - sigval_t this doesn't exist in the standard
>>>>>>
>>>>>> Are you copying this from an older implementation ? There are too many
>>>>>> unexpected features in this patch. I need to understand what's this
>>>>>> all about before I continue reading the patches. I can't spend time
>>>>>> verifying that non standard code is being submitted, this has to be
>>>>>> done by the contributor.
>>>>>>
>>>>>> 2009/6/12 Henrique Almeida <hd...@gm...>:
>>>>>>>  Comments for commit:
>>>>>>>
>>>>>>>  9a0a36a4cbfdea5f8666cf52747fb7dc317258ab fixed i386 build.
>>>>>>>
>>>>>>>  - uncomment #ifdef in syscall_nums.h
>>>>>>>  - vsyscall address in being overwritten in line 108, movl 28(%ebp), %edi
>>>>>>>
>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>>  Broken branch updated up to 2009-06-05
>>>>>>>>
>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>>>  Comments for commit:
>>>>>>>>>
>>>>>>>>>  3ea871f2ae8e772127d0d2434f027ad4d2586678 implemented strrchr()
>>>>>>>>> including unit tests.
>>>>>>>>>
>>>>>>>>>  on strrchr.c, '\0' must be considered part of the string, fix both
>>>>>>>>> the implementation and test
>>>>>>>>>
>>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>>>>  Comments for commit:
>>>>>>>>>>
>>>>>>>>>>  d808005b6f54ae16bdc5e18d4604afe6c6d7949d added unit tests for already
>>>>>>>>>> implemented str* functions.
>>>>>>>>>>
>>>>>>>>>>  - remove test prefix from file names
>>>>>>>>>> - test.strchr1.c third test (TEST_ASSERT(strchr(buf, '\0')==NULL)) is
>>>>>>>>>> incorrect, fix to TEST_ASSERT(strchr(buf, '\0')==buf+13
>>>>>>>>>> - add test coverage to strcmp: range 0, UCHAR_MAX
>>>>>>>>>> - add test coverage to strcpy: out of bound writes (both sides)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>>>>>  Comments for commit:
>>>>>>>>>>>
>>>>>>>>>>>  1d146af4f761c6c43dbc911fca0b8fbe7d7f487d added mmap and munmap.
>>>>>>>>>>>
>>>>>>>>>>> - sys/mman.h
>>>>>>>>>>>  - the PROT_* macros are system dependent (they depend on the kernel used).
>>>>>>>>>>>   mman.h should be moved to the system directory. Also, the reference for
>>>>>>>>>>>   the values for linux are missing.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2009/6/9 Henrique Almeida <hd...@gm...>:
>>>>>>>>>>>>
>>>>>>>>>>>>  I have done a git pull here and there are individual commits. I think I
>>>>>>>>>>>> haven't noticed them earlier. I'll begin to read each of them.
>>>>>>>>>>>>
>>>>>>>>>>>> 2009/6/8 Henrique Almeida <hd...@gm...>
>>>>>>>>>>>>>
>>>>>>>>>>>>>  The problem was that the merge was condensed into a single commit (or
>>>>>>>>>>>>> maybe I didn't notice the other commits in the log). I can try again later,
>>>>>>>>>>>>> but at the moment there are some merge issues to resolve.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2009/6/8 Andreas Krennmair <akr...@go...>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> If there are differences, you always need an extra merge commit, as far
>>>>>>>>>>>>>> as I understand.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sat, Jun 6, 2009 at 10:40 PM, Henrique Almeida <hd...@gm...>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>  With git pull, I'm not being able to merge each commit individually in
>>>>>>>>>>>>>>> my branch:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>  commit 3c75fe8dccc28d9011bb8f5a548db0778eae54cd
>>>>>>>>>>>>>>> Merge: 1faac1a... 05b56ea...
>>>>>>>>>>>>>>> Author: Henrique <hd...@us...>
>>>>>>>>>>>>>>> Date:   Sat Jun 6 17:29:37 2009 -0300
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>     Merge git://github.com/akrennmair/libposix into andreas
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>     * git://github.com/akrennmair/libposix:
>>>>>>>>>>>>>>>       implemented abs(), labs() and llabs() including unit tests.
>>>>>>>>>>>>>>>       implemented strrchr() including unit tests.
>>>>>>>>>>>>>>>       fixed build dependencies for tests.
>>>>>>>>>>>>>>>       added unit tests for already implemented str* functions.
>>>>>>>>>>>>>>>       added mmap and munmap.
>>>>>>>>>>>>>>>       added simple unit tests for already implemented mem* functions.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>  Is there a way to fix this ?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2009/6/5 Henrique Almeida <hd...@gm...>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>  Ok, good idea, git branches rock !
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 2009/6/5 Andreas Krennmair <akr...@go...>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hello everybody,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> As the "broken" branch didn't work out as expected, I found a better
>>>>>>>>>>>>>>>>> way that both satisfies me in its abilities and also allows other developers
>>>>>>>>>>>>>>>>> to easily see and merge my changes. I have a fork of libposix uploaded on
>>>>>>>>>>>>>>>>> GitHub: http://github.com/akrennmair/libposix/tree/master
>>>>>>>>>>>>>>>>> In this fork, I will regularly keep track of changes in the official
>>>>>>>>>>>>>>>>> libposix git repository. But it's also simple to merge my commits into the
>>>>>>>>>>>>>>>>> official libposix repository by executing
>>>>>>>>>>>>>>>>> git pull git://github.com/akrennmair/libposix.git master
>>>>>>>>>>>>>>>>> in a clone of the official libposix git repository. Anyway, GitHub is
>>>>>>>>>>>>>>>>> the place to see and track my changes. Of course, this shall NOT be
>>>>>>>>>>>>>>>>> interpreted as a way to get independent from the official project, it is
>>>>>>>>>>>>>>>>> merely a way that helps me work in a more flexible fashion on the things
>>>>>>>>>>>>>>>>> that I want to work on, plus it makes my changes more visible and also
>>>>>>>>>>>>>>>>> easier to reintegrate with the official development line.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Nevertheless, I will continue posting short notifications about the
>>>>>>>>>>>>>>>>> things I currently work on to keep everyone informed. So far, I've worked on
>>>>>>>>>>>>>>>>> some simple functions including unit tests, and I hope to present a simple
>>>>>>>>>>>>>>>>> implementation of malloc(), free(), realloc() and calloc() within a day or
>>>>>>>>>>>>>>>>> two.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>> Andreas
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>>>>>>>>>> latest
>>>>>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>>>>>>>> Lib...@li...
>>>>>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>>>>>>> hd...@gm...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>>>>>> hd...@gm...
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the
>>>>>>>>>>>>>>> latest
>>>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>>>>>> Lib...@li...
>>>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>>>>>> OpenSolaris 2009.06 is a cutting edge operating system for enterprises
>>>>>>>>>>>>>> looking to deploy the next generation of Solaris that includes the latest
>>>>>>>>>>>>>> innovations from Sun and the OpenSource community. Download a copy and
>>>>>>>>>>>>>> enjoy capabilities such as Networking, Storage and Virtualization.
>>>>>>>>>>>>>> Go to: http://p.sf.net/sfu/opensolaris-get
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> Libposix-development mailing list
>>>>>>>>>>>>>> Lib...@li...
>>>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>>>> hd...@gm...
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Henrique Dante de Almeida
>>>>>>>>>>>> hd...@gm...
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>>  Henrique Dante de Almeida
>>>>>>>>>>>  hd...@gm...
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>  Henrique Dante de Almeida
>>>>>>>>>>  hd...@gm...
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>  Henrique Dante de Almeida
>>>>>>>>>  hd...@gm...
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>  Henrique Dante de Almeida
>>>>>>>>  hd...@gm...
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>  Henrique Dante de Almeida
>>>>>>>  hd...@gm...
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>  Henrique Dante de Almeida
>>>>>>  hd...@gm...
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Crystal Reports - New Free Runtime and 30 Day Trial
>>>>>> Check out the new simplified licensing option that enables unlimited
>>>>>> royalty-free distribution of the report engine for externally facing
>>>>>> server and web deployment.
>>>>>> http://p.sf.net/sfu/businessobjects
>>>>>> _______________________________________________
>>>>>> Libposix-development mailing list
>>>>>> Lib...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Crystal Reports - New Free Runtime and 30 Day Trial
>>>>> Check out the new simplified licensing option that enables unlimited
>>>>> royalty-free distribution of the report engine for externally facing
>>>>> server and web deployment.
>>>>> http://p.sf.net/sfu/businessobjects
>>>>> _______________________________________________
>>>>> Libposix-development mailing list
>>>>> Lib...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>  Henrique Dante de Almeida
>>>>  hd...@gm...
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Crystal Reports - New Free Runtime and 30 Day Trial
>>>> Check out the new simplified licensing option that enables unlimited
>>>> royalty-free distribution of the report engine for externally facing
>>>> server and web deployment.
>>>> http://p.sf.net/sfu/businessobjects
>>>> _______________________________________________
>>>> Libposix-development mailing list
>>>> Lib...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Crystal Reports - New Free Runtime and 30 Day Trial
>>> Check out the new simplified licensing option that enables unlimited
>>> royalty-free distribution of the report engine for externally facing
>>> server and web deployment.
>>> http://p.sf.net/sfu/businessobjects
>>> _______________________________________________
>>> Libposix-development mailing list
>>> Lib...@li...
>>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>>
>>
>>
>>
>> --
>>  Henrique Dante de Almeida
>>  hd...@gm...
>>
>> ------------------------------------------------------------------------------
>> Crystal Reports - New Free Runtime and 30 Day Trial
>> Check out the new simplified licensing option that enables unlimited
>> royalty-free distribution of the report engine for externally facing
>> server and web deployment.
>> http://p.sf.net/sfu/businessobjects
>> _______________________________________________
>> Libposix-development mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libposix-development
>>
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Libposix-development mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libposix-development
>



-- 
 Henrique Dante de Almeida
 hd...@gm...