Comments (2)
I removed strerror
that causes this problem because of its high maintenance-cost. So it should be fixed with the latest commit.
I will soon release patch v3.8.1 after CI passes (maybe a few hours later).
Background:
strerror
is used only when you pass FILE*
to toml::parse
instead of std::string filename
, std::filesystem::path
, or std::istream
.
There are multiple variants of strerror
depending on the environment. The standard version is not thread-safe, so some compilers complain about it (already reported). To avoid this problem, we use environment-specific macros to detect which one is available. But I found that there are multiple environments/conditions where we cannot detect the available variant of strerror
using de-facto macro (actually, we have just fixed the same kind of problem yesterday, before the release). There can be more envs where this does not work. The benefit of using strerror
is not worth the cost.
I think the FILE*
version is less used than other overloads (most of the users may not even know such an overload exists). And the impact is even smaller, since the change does not remove the ability to pass FILE*
, but only to return an error number instead of a string if it fails. Still, one can search for the error number, or can get the errno from the exception and call the variant of strerror
that is appropriate in the environment.
from toml11.
released.
from toml11.
Related Issues (20)
- Serialization issue with floating values and locale HOT 1
- TOML11_DEFINE_CONVERSION_NON_INTRUSIVE save files HOT 2
- I'd like to retrieve uint64_t that exceed the range of int64_t HOT 1
- New version? HOT 3
- Weird serialization issue with strings that are file paths HOT 1
- Building with C++20 and the following error is triggered HOT 1
- When trying to use your tests / examples, there are no `*.toml` files in the repo HOT 1
- force arrays to be inline
- Warning: Moving a temporary object prevents copy elison with g++ 13.2.1 HOT 1
- Different `strerror_r` function usage HOT 7
- toml::parse() sould be able to read everything that serializer outputs HOT 1
- User-defined error messages and generic hints HOT 1
- User-defined error messages conflict with built-in hints HOT 1
- `toml::format` returns the wrong floating value HOT 2
- Preserve hex number format HOT 1
- Requiring CMAKE_CXX_STANDARD is a bug, not a feature
- Segmentation fault while parsing a TOML file
- Haven't overload "=" operator for toml::table HOT 1
- Improve "unknown value appeared" error message
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from toml11.