Re: Things to hack on?

Tom Lord <lord-1tv/[email protected]> writes:

>     > From: Andreas Rottmann <[email protected]>
>
>     > > One idea is to move those to src/libscm, review/unrot them, and write
>     > > some tests.   The code in there that does interrupt polling can just
>     > > be #if 0'ed out for now (and add a #undef FIXME there too -- to make
>     > > it easier to grep for).
>
>     > OK, I'm on it. Should the functions live in libscm/pair.c? Also, is
>     > a unit test called pair-tests/unit-lists.c OK?
>
> Yes, and yes.
>
One more question: jivera has branches for each area he hacks on
(number, strings, ...). Should I do the same (i.e. create a list
branch) or just commit to my integration branch? I guess its the
former, but just to be sure.

Andy
-- 
Andreas Rottmann         | [email protected]      | 118634484@ICQ | [email protected]
http://yi.org/rotty      | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62

Make free software, not war!