Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HedgeLib++ - Pick an XML Parser #46

Open
Radfordhound opened this issue Jan 15, 2019 · 0 comments
Open

HedgeLib++ - Pick an XML Parser #46

Radfordhound opened this issue Jan 15, 2019 · 0 comments

Comments

@Radfordhound
Copy link
Owner

We'll need to read/write XML files in HedgeLib. As we're not using the .NET framework anymore, we can't use the .NET framework XML stuff, so we'll have to find an XML library under a usable license (or write our own but I'm not planning on doing that lol).

I did a quick Google search and found several good-looking options we could use:

  • RapidXML (Under your choice of MIT License or Boost License, very widely used, not really supported anymore).
  • pugixml (Under the MIT License, very actively supported).
  • TinyXML-2 (Under the zlib License, actively supported).

All of these do what we need them to (to my knowledge, anyway), and they're all pretty popular and very fast, so it's really just a matter of picking which one to use.

I'm kind of thinking pugixml tbh as it seems easiest to use, and these benchmarks look fantastic (though I realize these results could be biased as they're on the official pugixml site), but I'm wanting to hear from you on this first. Which do you think would be best?

@Radfordhound Radfordhound added this to the HedgeLib++ 1.0 milestone Jan 15, 2019
@Radfordhound Radfordhound added this to To do (High Priority) in HedgeLib++ Jan 15, 2019
@Radfordhound Radfordhound changed the title HedgeLib++ - Picking an XML Parser HedgeLib++ - Pick an XML Parser Jan 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
HedgeLib++
  
To do (High Priority)
Development

No branches or pull requests

1 participant