From: Kevin Ryde <user42@zip.com.au>
Subject: Re: ice-9 gap-buffer and substring-move
Date: Mon, 12 May 2003 08:17:38 +1000 [thread overview]
Message-ID: <87d6ip86wt.fsf@zip.com.au> (raw)
In-Reply-To: 871xzfd8lg.fsf@zagadka.ping.de
[-- Attachment #1: Type: text/plain, Size: 318 bytes --]
Marius Vollmer <mvo@zagadka.de> writes:
>
> substring-move-left! and -right! have just returned, as
> deprecated functions,
I guess the news file can be updated accordingly (below).
(That news file is pretty big, almost 1000 lines back to version 1.6.
I suspect a good fraction of that text belongs in the manual.)
[-- Attachment #2: NEWS.substring-move.diff --]
[-- Type: text/plain, Size: 463 bytes --]
--- NEWS.~1.389.~ 2003-05-03 09:15:32.000000000 +1000
+++ NEWS 2003-05-11 13:51:03.000000000 +1000
@@ -482,10 +482,6 @@
You can now use an empty `begin' form. It will yield #<unspecified>
when evaluated and simply be ignored in a definition context.
-** Removed: substring-move-left!, substring-move-right!
-
-Use `substring-move!' instead.
-
** Deprecated: procedure->macro
Change your code to use either procedure->memoizing-macro or, probably better,
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-11 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 22:58 ice-9 gap-buffer and substring-move Kevin Ryde
2003-05-03 21:27 ` Marius Vollmer
2003-05-11 22:17 ` Kevin Ryde [this message]
2003-05-16 23:41 ` 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=87d6ip86wt.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).