From: Kevin Ryde <user42@zip.com.au>
Subject: Re: `scm_list ()'
Date: Fri, 03 Feb 2006 08:25:55 +1100 [thread overview]
Message-ID: <87d5i5qwpo.fsf@zip.com.au> (raw)
In-Reply-To: <87ek2mumle.fsf@laas.fr> (Ludovic Courtès's message of "Thu, 02 Feb 2006 10:38:37 +0100")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
>
> The funny thing is that to get a list, you had to have a list already
> (OBJS is a list here). I don't really get the point of this function in
> fact. ;-)
That's why I dropped it :-). But yes, I'll put it back just in case.
> scm_c_issue_deprecation_warning ("`scm_list' is deprecated. Use "
> "`scm_list_n' instead.");
> SCM_VALIDATE_LIST (1, obj);
No thanks, I'll put the original no-op.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-02-02 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 9:38 `scm_list ()' Ludovic Courtès
2006-02-02 18:58 ` Neil Jerram
2006-02-02 21:25 ` Kevin Ryde [this message]
2006-02-06 9:15 ` Ludovic Courtès
2006-02-06 20:26 ` Kevin Ryde
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=87d5i5qwpo.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).