Am Wednesday, 17. August 2011, 13:42:50 schrieb Carl Sorensen:
> On 8/17/11 5:35 AM, "David Kastrup" wrote:
> > So it would seem like another worthwhile frog task to get rid of
> > SCM_CDRLOC in the source tree when feasible (when the list is being
> > consulted front-to-back while it is in the pr
On 8/17/11 5:35 AM, "David Kastrup" wrote:
>
> So it would seem like another worthwhile frog task to get rid of
> SCM_CDRLOC in the source tree when feasible (when the list is being
> consulted front-to-back while it is in the process of being created,
> this would not be possible. However, si
I just profiled the following code:
#include
#include
void *test1(void *n)
{
for (int i=0; i<(int)n; i++) {
SCM list = SCM_EOL;
SCM *tail = &list;
for (int k=0; k<(int)n; k++) {
*tail = scm_cons (SCM_BOOL_F, SCM_EOL);
tail = SCM_CDRLOC(*tail);
}
}
return 0;
}
