boost-xpressive

Boost::Xpressive compile puzzle under MinGW

大憨熊 提交于 2019-12-23 03:07:28
问题 Switching to GCC for the first time, and I'm getting a bit confused by what the compiler is telling me here. Essentially, it's behaving like boost::xpressive::wsregex is not defined (I believe). Here is the relevant code: #include "criterion.h" #include <string> #include <boost/xpressive/xpressive.hpp> //More lines of code omitted here class perlRegex : public regexClass { private: std::wstring regexString; boost::xpressive::wsregex regex; // This is the line complained about public: unsigned

regex: boost::xpressive vs boost::regex

一世执手 提交于 2019-12-21 07:14:24
问题 I wanted to do some regular expressions in C++ so I looked on the interwebz (yes, I am an beginner/intermediate with C++) and found this SO answer. I really don't know what to choose between boost::regex and boost::xpressive. What are the pros/cons? I also read that boost::xpressive opposed to boost::regex is a header-only library. Is it hard to statically compile boost::regex on Linux and Windows (I almost always write cross-platform applications)? I'm also interested in comparisons of

regex: boost::xpressive vs boost::regex

别等时光非礼了梦想. 提交于 2019-12-04 00:15:43
I wanted to do some regular expressions in C++ so I looked on the interwebz (yes, I am an beginner/intermediate with C++) and found this SO answer . I really don't know what to choose between boost::regex and boost::xpressive. What are the pros/cons? I also read that boost::xpressive opposed to boost::regex is a header-only library. Is it hard to statically compile boost::regex on Linux and Windows (I almost always write cross-platform applications)? I'm also interested in comparisons of compile time. I have a current implementation using boost::xpressive and I'm not too content with the

Slow performance using boost xpressive

夙愿已清 提交于 2019-11-28 06:52:42
问题 Lately I have being using boost xpressive for parsing files. These files are 10 MB each and there will be several hundred of them to parse. Xpressive is nice to work and clear syntax, but the problems comes with performance. It is incredible how it crawls in debug versions, while in release version it spends more than a whole second per file. I have tested against old plain get_line(), find() and sscanf() code, and it can beat xpressive easily. I understand that type checking, backtracking

How to parse mustache with Boost.Xpressive correctly?

只愿长相守 提交于 2019-11-27 23:22:25
I have tried to write a mustache parser with the excellent Boost.XPressive from the brilliant Eric Niebler . But since this is my first parser I am not familiar with the "normal" approach and lingo of compiler writers and feel a bit lost after a few days of trial&error. So I come here and hope someone can tell me the foolishness of my n00bish ways ;) This is the HTML code with the mustache templates that I want to extract ( http://mustache.github.io/ ): Now <bold>is the {{#time}}gugus {{zeit}} oder nicht{{/time}} <i>for all good men</i> to come to the {007} aid of their</bold> {{country}}.

How to parse mustache with Boost.Xpressive correctly?

谁都会走 提交于 2019-11-26 23:18:16
问题 I have tried to write a mustache parser with the excellent Boost.XPressive from the brilliant Eric Niebler . But since this is my first parser I am not familiar with the "normal" approach and lingo of compiler writers and feel a bit lost after a few days of trial&error. So I come here and hope someone can tell me the foolishness of my n00bish ways ;) This is the HTML code with the mustache templates that I want to extract (http://mustache.github.io/): Now <bold>is the {{#time}}gugus {{zeit}}