Update util.h #2
Merged
+1
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add <string> header to use std::string. Needed for compilation with g++.
|
Many thanks! Yes, I sort of accidentaly invented the xmq format while reading tons of xml code and trying to figure out a way to make my life easier. I use xmq-less every day now.... Then, as you say, I have several times felt (in particular when I have to edit yaml files) that I should use the xmq format directly for my config files etc. Please open a Rust issue and we can put in a rust version. I intend to write a Java and Javascript parser versions as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add "string" header to use std::string. Needed for compilation with g++. Btw, I really like the syntax of xmq a lot for a data language. Im considering porting xmq to rust. It really shines in comparison to toml, json, xaml and xml. It comes without quotes, does not enforce indents and is readable with any depth. YAML becomes unreadable after 2 indents, TOML + JSON use too many quotes, TOML has no convenience over nesting, XML is too verbose with endtags (while offering best complexity). Neat! XMQ addresses all these problems and is extremely human readable.