From: Kevin Ryde <user42@zip.com.au>
Subject: Re: srfi-1 take and drop
Date: Thu, 08 May 2003 10:00:33 +1000 [thread overview]
Message-ID: <87ptmuwbmm.fsf@zip.com.au> (raw)
In-Reply-To: <87issoydv3.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Mon, 05 May 2003 22:04:48 -0500")
Rob Browning <rlb@defaultvalue.org> writes:
>
> Yep, I have a "take" I haven't committed yet that avoids both stack
> growth and reverse! by tracking the end pair...
Is that the same as what list-head does (in C)?
Can save some work ... :-).
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-08 0:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 23:14 srfi-1 take and drop Kevin Ryde
2003-05-06 1:30 ` Rob Browning
2003-05-06 1:58 ` Kevin Ryde
2003-05-06 3:02 ` Rob Browning
2003-05-06 3:04 ` Rob Browning
2003-05-08 0:00 ` Kevin Ryde [this message]
2003-05-08 16:37 ` Rob Browning
2003-05-09 22:38 ` Kevin Ryde
2003-05-08 16:12 ` Paul Jarc
2003-05-08 16:35 ` Rob Browning
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ptmuwbmm.fsf@zip.com.au \
--to=user42@zip.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).