Re: [Pika-dev] Things to hack on?

[Andreas Rottmann]

Tom Lord <address@hidden> writes:

> One idea is to move those to src/libscm, review/unrot them, and write
> some tests.
>
OK, have done that now. Changeset is pika-scm--lists--0.1--patch-1:

* Moved scm_is_list() and scm_list_ilength() from
  unfinished-code/libscm/pairs.c to libscm/pairs.c, unrotted and
  polished them.

* Implemented scm_is_circular_list().

* New unit test test/pair-tests/unit-lists.c, which covers above
  functionality.

Don't bother with it, if you don't really need it, there is more stuff
on the line.

> 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).
>
Done. Just out of curiosity: what are "interrupts" for? (haven't found
anything explanatory with a quick grep)

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

Latein ist das humanoide Äquivalent zu Fortran.
   -- Alexander Bartolich in at.linux