unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Guile 2 deprecated procedure and SLIB
Date: Fri, 08 Feb 2013 10:32:04 +0100	[thread overview]
Message-ID: <87k3qj2lt7.fsf@pobox.com> (raw)
In-Reply-To: <87pq0b7au3.fsf@tines.lan> (Mark H. Weaver's message of "Thu, 07 Feb 2013 22:17:56 -0500")

On Fri 08 Feb 2013 04:17, Mark H Weaver <mhw@netris.org> writes:

> Andy Wingo <wingo@pobox.com> writes:
>
>> On Sat 02 Feb 2013 00:03, Andrew Bernard <andrew.bernard@gmail.com> writes:
>>
>>> In the latest top CVS of SLIB (as of Feb 2013), with Guile 2.0.7, the
>>> procedure used in the common lisp time section decode-universal-time use
>>> the deprecated procedure list->uniform-array.
> [...]
>>> I am new to Scheme, and not sure how to handle this. Not wanting to
>>> enable the use of deprecated procedures, how does one proceed?
>>
>> Deprecated procedures are enabled by default; you'd have to do something
>> special to disable them.  For now I would just deal with it or file a
>> patch with SLIB to replace this function.
>
> Unfortunately, 'list->uniform-array' is not merely deprecated; it has
> been removed entirely from Guile 2.0.

Ah, you are correct.  Deprecated around 2005-01-10 by Marius, and
removed by me in 2009 with 86d88a223c64276e7cd9b4503e7e2ecca5aae320.

NEWS says that list->typed-array is the thing to use instead.

Andy
-- 
http://wingolog.org/



      reply	other threads:[~2013-02-08  9:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 23:03 Guile 2 deprecated procedure and SLIB Andrew Bernard
2013-02-04 11:19 ` Andy Wingo
2013-02-07 20:50   ` Mikael Djurfeldt
2013-02-08  8:22     ` Andy Wingo
2013-02-08  8:40       ` Mikael Djurfeldt
2013-02-08  3:17   ` Mark H Weaver
2013-02-08  9:32     ` Andy Wingo [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=87k3qj2lt7.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-user@gnu.org \
    --cc=mhw@netris.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).