[spirit] warnings after upgrade to 1.47
Dear all, After upgrading to boost 1.47, I got the attached enormous warning, ironically saying that names are too long, for a very simple use of boost.spirit. Code: #include <string> #include <vector> using namespace std; #include <boost/spirit/include/karma.hpp> namespace bsk = boost::spirit::karma; namespace bsa = boost::spirit::ascii; vector<string> vUnrecog; //... bsk::generate(ostream_iterator<char>(cout), "Init file options not recognized:\n" << (" \"" << bsa::string << '"' << bsk::eol) % "", vUnrecog); Is there something I am doing suboptimally or in an old way? (The code has been around for about 2 years now). Thanks and best, Dee
After upgrading to boost 1.47, I got the attached enormous warning, ironically saying that names are too long, for a very simple use of boost.spirit. Code:
#include <string> #include <vector> using namespace std; #include <boost/spirit/include/karma.hpp> namespace bsk = boost::spirit::karma; namespace bsa = boost::spirit::ascii;
vector<string> vUnrecog; //... bsk::generate(ostream_iterator<char>(cout), "Init file options not recognized:\n" << (" \"" << bsa::string << '"' << bsk::eol) % "", vUnrecog);
Is there something I am doing suboptimally or in an old way? (The code has been around for about 2 years now).
It's not your fault, but not ours either :-P Spirit V2.5 (as in V1.47) has been partially rewritten to straighten out a couple of wrinkles and to fix some problems. I believe that's the reason why you're starting to see these warnings now. The only thing I could think of as a workaround is to disable that warning for your code, either via the command line or using #pragma warning(). Regards Hartmut --------------- http://boost-spirit.com
Hi Harmut, On Tue, Jul 19, 2011 at 22:27, Hartmut Kaiser <hartmut.kaiser@gmail.com> wrote:
It's not your fault, but not ours either :-P
Spirit V2.5 (as in V1.47) has been partially rewritten to straighten out a couple of wrinkles and to fix some problems. I believe that's the reason why you're starting to see these warnings now.
The only thing I could think of as a workaround is to disable that warning for your code, either via the command line or using #pragma warning().
Thanks, a "#pragma warning(disable:4503)" did the trick and the code does its job just fine (as the help for that warning says it should). Best, Dee
participants (2)
-
Diederick C. Niehorster
-
Hartmut Kaiser