Warnings `_IOFBF' is deprecated. Use the symbol 'block instead.

Warnings `_IOFBF' is deprecated. Use the symbol 'block instead.

[Roel Janssen]

Dear Guilers,

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?

Kind regards,
Roel Janssen

Re: Warnings `_IOFBF' is deprecated. Use the symbol 'block instead.

[Ludovic Courtès]

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

Re: Warnings `_IOFBF' is deprecated. Use the symbol 'block instead.

[Roel Janssen]

Ludovic Courtès <ludo@gnu.org> writes:

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

Thanks for your response.  So, since my project relies quite heavily on
Guix, I guess I can only disable deprecation warnings too.  Will this be
a problem for Guile 3.0?

Thanks for your quick response!

Kind regards,
Roel Janssen

Re: Warnings `_IOFBF' is deprecated. Use the symbol 'block instead.

[Ludovic Courtès]

Roel Janssen <roel@gnu.org> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> 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’.
>
> Thanks for your response.  So, since my project relies quite heavily on
> Guix, I guess I can only disable deprecation warnings too.

Possibly.  It’s a good thing to in CLIs anyway because that’s not
something the user can do anything about.

The plan is for Guix to require Guile >= 2.2 sometime soon though, so at
that point we can move to the new APIs.

> Will this be a problem for Guile 3.0?

Features deprecated in a stable series may be removed in the next stable
series, though in this particular case I would argue for keeping it a
bit longer.

Thanks,
Ludo’.

Re: Warnings `_IOFBF' is deprecated. Use the symbol 'block instead.

[Hans Åberg]

> On 13 Jul 2018, at 10:13, Ludovic Courtès <ludo@gnu.org> wrote:
> 
> The plan is for Guix to require Guile >= 2.2 sometime soon though, so at
> that point we can move to the new APIs.

A bug that may or may not be carried over to Guix: I could not install Nix on MacOS 10.13, and I think it may be due to the sudo timeout set to zero, causing non-terminating confirmations. So the script may do more root calls than explicitly asked for, a potential security loophole.

Re: Warnings `_IOFBF' is deprecated. Use the symbol 'block instead.

[Ludovic Courtès]

Hans Åberg <haberg-1@telia.com> skribis:

>> On 13 Jul 2018, at 10:13, Ludovic Courtès <ludo@gnu.org> wrote:
>> 
>> The plan is for Guix to require Guile >= 2.2 sometime soon though,
>> so at that point we can move to the new APIs.
>
> A bug that may or may not be carried over to Guix: I could not install
> Nix on MacOS 10.13, and I think it may be due to the sudo timeout set
> to zero, causing non-terminating confirmations. So the script may do
> more root calls than explicitly asked for, a potential security
> loophole.

We’ve changed topics, right?  :-)

I don’t know what Nix is doing.  Guix works only on systems running the
kernel Linux or the GNU Hurd, anyway.

Ludo’.

Re: Warnings `_IOFBF' is deprecated. Use the symbol 'block instead.

[Hans Åberg]

> On 13 Jul 2018, at 16:44, Ludovic Courtès <ludo@gnu.org> wrote:
> 
> Hans Åberg <haberg-1@telia.com> skribis:
> 
>>> On 13 Jul 2018, at 10:13, Ludovic Courtès <ludo@gnu.org> wrote:
>>> 
>>> The plan is for Guix to require Guile >= 2.2 sometime soon though,
>>> so at that point we can move to the new APIs.
>> 
>> A bug that may or may not be carried over to Guix: I could not install
>> Nix on MacOS 10.13, and I think it may be due to the sudo timeout set
>> to zero, causing non-terminating confirmations. So the script may do
>> more root calls than explicitly asked for, a potential security
>> loophole.
> 
> We’ve changed topics, right?  :-)

Right. :-)

> I don’t know what Nix is doing.  Guix works only on systems running the
> kernel Linux or the GNU Hurd, anyway.

It is only a problem if you have an installer for whatever system. The suggestion is to test the installation with sudo timeout set to 0.