Roel Janssen <r...@gnu.org> skribis: > Ludovic Courtès <l...@gnu.org> writes: > >> Hello, >> >> Roel Janssen <r...@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’.
