You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
seems that the library always adds a "global" section, even for empty files.
This is surprising because it's not mentioned in the readme, nor in the api docs
The way it is implemented seems particularly worrisome. While I can see how we would want a place to keep globally/un-sectioned parameters, the current approach means you cannot distinguish global parameters from a real global section.
for example the below program will print the section as foo=42, whether that parameter was declared globally or in a section literally called [global]
(full output after source code)
fixalyu#8
Note: this does not update a bunch of functions to query for sections
etc, modify them, etc. Those currently don't have access to the new
global section.
Hello,
seems that the library always adds a "global" section, even for empty files.
This is surprising because it's not mentioned in the readme, nor in the api docs
The way it is implemented seems particularly worrisome. While I can see how we would want a place to keep globally/un-sectioned parameters, the current approach means you cannot distinguish global parameters from a real global section.
for example the below program will print the section as
foo=42
, whether that parameter was declared globally or in a section literally called[global]
(full output after source code)
The text was updated successfully, but these errors were encountered: