[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Pika-dev] Things to hack on?
From: |
Andreas Rottmann |
Subject: |
Re: [Pika-dev] Things to hack on? |
Date: |
Mon, 02 Feb 2004 19:23:55 +0100 |
User-agent: |
Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) |
Tom Lord <address@hidden> writes:
> > From: Andreas Rottmann <address@hidden>
>
> > I just wonder what's up next for implementation in Pika; I could
> > imagine hacking on:
>
> scm_is_list () and scm_list_length () might be a good place to start.
>
[snip description of unfinished-code]
> 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?
> scm_list_reverse can work similarly.
>
> It might be worth modifying scm_list_ilength to optionally return the
> last pair of a proper list and then use that to write scm_list_append.
>
OK, I'll consider that.
Andy
--
Andreas Rottmann | address@hidden | address@hidden | address@hidden
http://yi.org/rotty | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
Say NO to Software Patents! -- http://petition.eurolinux.org/
Re: [Pika-dev] Things to hack on?, Matthew Dempsky, 2004/02/02