Re: Odd behaviour of char_ parser?

Mikael Asplund <[email protected]>
Newsgroups gmane.comp.parsers.spirit.general
Message-ID <[email protected]>
What Mike's saying is that you have made a mistake translating the character f into a code point... your example says:

"\x60\x6f"   which is not the same as "fo", but instead "`o".  You should use "\x66\x6f", and it should work.

  /Mikael

-----Original Message-----
From: Jay Pipes [mailto:[email protected]] 
Sent: Tuesday, December 13, 2016 13:53
To: [email protected]
Subject: Re: [Spirit-general] Odd behaviour of char_ parser?

On 12/13/2016 02:03 AM, Mike Gresens wrote:
> Hi,
>
> "fo" should be "\x66\x6f".

It's the "fo" parser that works. The one with the code points is the one that doesn't parse.

Best,
-jay

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________
Spirit-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/spirit-general

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.