From: Marius Vollmer <mvo@zagadka.de>
Subject: Re: srfi-1 delete-duplicates
Date: 27 Jul 2003 17:11:20 +0200 [thread overview]
Message-ID: <87k7a4romf.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87u1ajklju.fsf@zip.com.au>
Kevin Ryde <user42@zip.com.au> writes:
> This is new delete-duplicates and delete-duplicates!, avoiding the
> non-tail-recursions of the current implementations.
Excellent!
While it certainly can't hurt to implement functions in C and I am
sure you know this already, I still want to point out that avoiding
non-tail-recursive behavior does of course not imply having to code
the thing in C.
So, when spotting a non-tail-recursive function that should be
tail-recursive, the easy thing would be to change the Scheme code.
One does not need to recode it completely in C.
Just something that I thought of.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-07-27 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 0:23 srfi-1 delete-duplicates Kevin Ryde
2003-07-27 15:11 ` Marius Vollmer [this message]
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=87k7a4romf.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
/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).