From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org
Subject: Re: srfi-17 generates "deprecated" warnings
Date: Fri, 18 Mar 2005 08:22:13 +1100 [thread overview]
Message-ID: <87r7ieezne.fsf@zip.com.au> (raw)
In-Reply-To: <4238F5D7.2060801@mail.msen.com> (Alan Grover's message of "Wed, 16 Mar 2005 22:13:27 -0500")
Alan Grover <awgrover@mail.msen.com> writes:
>
> + :re-export (setter))
I think that has to be an export at the end, since it's a redefinition
of a core procedure.
> +(export
> + ;; redefined standard procedures
> + car cdr caar cadr cdar cddr caaar caadr cadar caddr cdaar
> + cdadr cddar cdddr caaaar caaadr caadar caaddr cadaar cadadr
> + caddar cadddr cdaaar cdaadr cdadar cdaddr cddaar cddadr
> + cdddar cddddr string-ref vector-ref)
Thanks, I made that change.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2005-03-17 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 3:13 srfi-17 generates "deprecated" warnings Alan Grover
2005-03-17 21:22 ` Kevin Ryde [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=87r7ieezne.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=bug-guile@gnu.org \
/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).