Hi I've now been fighting for two days with TOML and its C++ library and I've come to the conclusion that JSON would be the better format for us for many reasons, which would be for instance: * Easier to express hierarchical lists. * More reliable library support
@Hagen: I'm tempted to port your TOML file over to JSON, if that's ok with you.
Cheers David
Hello David.
On 03/20/2018 12:12 PM, David Lanzendörfer wrote:
I've now been fighting for two days with TOML and its C++ library and I've come to the conclusion that JSON would be the better format for us for many reasons, which would be for instance:
- Easier to express hierarchical lists.
- More reliable library support
Well, there is one big reason why I like TOML even more than JSON.
JSON does not have the capability to contain comments, might be from line start on or after sign 'till end of line. See RFC 4627, RFC 7159.
So JSON looks nice in the first place, but it is far from being human-readable as it always noted.
Every source code without the possibility to add comments or notes belongs to the stone-age!
hierarchical list TOML also can doing, see https://gist.github.com/robmuh/7966da29024c075349a963840e2298b2
@Hagen: I'm tempted to port your TOML file over to JSON, if that's ok with you.
)-:
Please have a look at http://alexcrichton.com/toml-rs/toml/index.html
The nice and fancy language Rust has TOML for their library support. What a beauty! So hopefully David, you'll take the challenge and give as a TOML parser. Might be, just my TOML file is not syntactical correct?
Regards, Hagen
Hi Well. Maybe it's really just that your syntax is off or that the C++ library I've been trying out doesn't support this feature yet. Okey... I agree: The lack of comments is a real show stopper
Cheers David
On Tuesday, 20 March 2018 7:30:43 PM HKT Hagen SANKOWSKI wrote:
Hello David.
On 03/20/2018 12:12 PM, David Lanzendörfer wrote:
I've now been fighting for two days with TOML and its C++ library and I've come to the conclusion that JSON would be the better format for us for many> reasons, which would be for instance:
- Easier to express hierarchical lists.
- More reliable library support
Well, there is one big reason why I like TOML even more than JSON.
JSON does not have the capability to contain comments, might be from line start on or after sign 'till end of line. See RFC 4627, RFC 7159.
So JSON looks nice in the first place, but it is far from being human-readable as it always noted.
Every source code without the possibility to add comments or notes belongs to the stone-age!
hierarchical list TOML also can doing, see https://gist.github.com/robmuh/7966da29024c075349a963840e2298b2
@Hagen: I'm tempted to port your TOML file over to JSON, if that's ok with you.
)-:
Please have a look at http://alexcrichton.com/toml-rs/toml/index.html
The nice and fancy language Rust has TOML for their library support. What a beauty! So hopefully David, you'll take the challenge and give as a TOML parser. Might be, just my TOML file is not syntactical correct?
Regards, Hagen
Hi Hagen I fixed your TOML syntax: https://github.com/leviathanch/qtflow/blob/master/tech/ls1u.toml
This way I'm now able to access a table with all the layers
Cheers David
On Tuesday, 20 March 2018 7:30:43 PM HKT Hagen SANKOWSKI wrote:
Hello David.
On 03/20/2018 12:12 PM, David Lanzendörfer wrote:
I've now been fighting for two days with TOML and its C++ library and I've come to the conclusion that JSON would be the better format for us for many> reasons, which would be for instance:
- Easier to express hierarchical lists.
- More reliable library support
Well, there is one big reason why I like TOML even more than JSON.
JSON does not have the capability to contain comments, might be from line start on or after sign 'till end of line. See RFC 4627, RFC 7159.
So JSON looks nice in the first place, but it is far from being human-readable as it always noted.
Every source code without the possibility to add comments or notes belongs to the stone-age!
hierarchical list TOML also can doing, see https://gist.github.com/robmuh/7966da29024c075349a963840e2298b2
@Hagen: I'm tempted to port your TOML file over to JSON, if that's ok with you.
)-:
Please have a look at http://alexcrichton.com/toml-rs/toml/index.html
The nice and fancy language Rust has TOML for their library support. What a beauty! So hopefully David, you'll take the challenge and give as a TOML parser. Might be, just my TOML file is not syntactical correct?
Regards, Hagen
On 03/20/2018 03:07 PM, David Lanzendörfer wrote:
Hi Hagen I fixed your TOML syntax: https://github.com/leviathanch/qtflow/blob/master/tech/ls1u.toml
This way I'm now able to access a table with all the layers
Thanks!
libresilicon-developers@list.libresilicon.com
-
David Lanzendörfer -
Hagen SANKOWSKI