unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 27152@debbugs.gnu.org
Subject: bug#27152: deprecation warnings with Guile 2.2.2
Date: Fri, 2 Jun 2017 17:39:59 -0700	[thread overview]
Message-ID: <CAN-vT6T8_ajiXi0crfywO7sM8Wqj6+GmhgH3rYVn8-PT0BfBMA@mail.gmail.com> (raw)
In-Reply-To: <87h90091y4.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]

On Wed, May 31, 2017 at 2:00 PM, Ludovic Courtès <ludo@gnu.org> wrote:

> Hi,
>
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
> > I get a couple of deprecation warnings with Guile 2.2.2, for example
> >
> >     Import (ice-9 threads) to have access to `current-processor-count'.
> >     `_IOFBF' is deprecated.  Use the symbol 'block instead.
>
> We can fix the first one with #:use-module (ice-9 threads).
>
> The second one is just a pain: in 2.2 one is supposed to write
>
>   (setvbuf port 'block)
>
> instead of
>
>   (setvbuf port _IOFBF)
>
> So we could do:
>
>   (cond-expand (guile-2.2 (define _IOFBF 'block))
>                (else #t))
>

in some central place (that doesn’t exist), but really, that’s annoying.
>
> So I’m tempted to do nothing.
>
> Note that normally users do not see these deprecation warnings at all.
>
> Thoughts?
>

Why not let good old sed have a run at it? Seems like a simple find and
replace operation, and 'block looks nicer than _IOFBF to my eyes.

Maxim

[-- Attachment #2: Type: text/html, Size: 1701 bytes --]

  reply	other threads:[~2017-06-03  0:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 20:31 bug#27152: deprecation warnings with Guile 2.2.2 Ricardo Wurmus
2017-05-31 21:00 ` Ludovic Courtès
2017-06-03  0:39   ` Maxim Cournoyer [this message]
2017-06-03  1:20     ` Mark H Weaver
2017-06-03  4:43       ` Maxim Cournoyer
2017-06-04  5:18         ` Mark H Weaver
2017-06-04  5:51           ` Maxim Cournoyer
2017-06-04 22:04             ` Mark H Weaver

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAN-vT6T8_ajiXi0crfywO7sM8Wqj6+GmhgH3rYVn8-PT0BfBMA@mail.gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=27152@debbugs.gnu.org \
    --cc=ludo@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).