This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Gsoc 2014 project proposal
- From: Andrea Francesco Iuorio <andreafrancesco dot iuorio at gmail dot com>
- To: libc-alpha at sourceware dot org
- Date: Thu, 27 Feb 2014 10:27:19 +0100
- Subject: Re: Gsoc 2014 project proposal
- Authentication-results: sourceware.org; auth=none
- References: <CAMaJsKjobBfmxjBRB2WP6MMLiAAD=QTV3bhO=hogeZHxmmotPg at mail dot gmail dot com> <Pine dot LNX dot 4 dot 64 dot 1402261759390 dot 11728 at digraph dot polyomino dot org dot uk> <CAMaJsKg-4WTvX+XPYXMYXHZvRvUotyYeq7O69Xye4WBE7Zw6Wg at mail dot gmail dot com> <530ED801 dot 4000205 at redhat dot com>
2014-02-27 7:15 GMT+01:00 Carlos O'Donell <carlos@redhat.com>:
> I suggest *against* a precise plan. My strong suggestion is that you
> approach this tactically e.g. one function at a time. This way should
> you need to stop at any point the result is something that can be
> continued easily and the partial work is not lost.
>
> Adding the first function is the most work because it requires the
> new headers, and refactoring to get the types right.
>
> Cheers,
> Carlos.
>
So the "daily" workflow you suggest are:
1) Decide what function i want to implement and thinking what pthread
functionality i should need for this implementation.
2) Refactor pthread implementation
3) Implement the function
4) Write some tests and documentation.
Correct ? Point 4 i thought was taken for granted ( i didn' t know
glibc have its how testcase, but i can learn it ), but since you are
the second whom tell me about it i think i should rewrite better my
proposal. Thank you for your advices
--
Andrea Francesco Iuorio
Student in Computer Science, Università degli Studi di Milano
andreafrancesco.iuorio@gmail.com - GPG Key