From: ludo@gnu.org (Ludovic Courtès)
To: Roel Janssen <roel@gnu.org>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Warnings `_IOFBF' is deprecated. Use the symbol 'block instead.
Date: Thu, 12 Jul 2018 11:27:05 +0200 [thread overview]
Message-ID: <87h8l4x0ra.fsf@gnu.org> (raw)
In-Reply-To: <874lhadmxo.fsf@gnu.org> (Roel Janssen's message of "Sun, 08 Jul 2018 12:46:59 +0200")
Hello,
Roel Janssen <roel@gnu.org> skribis:
> When compiling my project, setting GUILE_WARN_DEPRECATED to "detailed",
> I get various warnings like these:
> `_IOFBF' is deprecated. Use the symbol 'block instead.
> `_IONBF' is deprecated. Use the symbol 'none instead.
> `_IOLBF' is deprecated. Use the symbol 'line instead.
>
> I grepped the source code of my project and I cannot find any instance
> of "_IOFBF", "_IONBF", and "_IOLBF".
>
> What's the situation with these, and how can I resolve these deprecation warnings?
You’re probably using a library (maybe Guix?) that uses those.
The problem is that these warnings are annoying, and getting rid them is
tedious if your code aims to be 2.0-compatible. Essentially you have to
use ‘cond-expand’ all around. :-/
In Guix we disable deprecation warnings.
Ludo’.
next prev parent reply other threads:[~2018-07-12 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 10:46 Warnings `_IOFBF' is deprecated. Use the symbol 'block instead Roel Janssen
2018-07-12 9:27 ` Ludovic Courtès [this message]
2018-07-12 20:41 ` Roel Janssen
2018-07-13 8:13 ` Ludovic Courtès
2018-07-13 12:45 ` Hans Åberg
2018-07-13 14:44 ` Ludovic Courtès
2018-07-13 15:51 ` Hans Åberg
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=87h8l4x0ra.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@gnu.org \
--cc=roel@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).