Re: IPv6 address parsing
Seth <[email protected]>
| Newsgroups | gmane.comp.parsers.spirit.general |
|---|---|
| Message-ID | <[email protected]> |
On 07-12-17 00:15, Michael Powell wrote:
> qi::rule<Iterator> _dec_octet = (
> char_('0')
> | char_('1') >> -(digit >> -digit)
> | char_('2') >> (
> char_('0', '4') >> -digit
> | char_('5') >> -char_('0', '5')
> | char_('6', '9')
> )
> | char_('3', '9') >> -digit
> );
Are you still using that contraption?! Why?
On 01-12-17 01:25, Seth wrote:
> On 30-11-17 14:32, Michael Powell wrote:
>> My goal is to parse address into a std::string. That will be important
>> for me when I turn the corner into IPv6 parsing. Could this approach
>> support that? i.e. uint_parser... into a std::string?
> Of course. Just slap `qi::raw[]` around the whole hot mess, and pronto.
> However, I explained exactly why I didn't do this. If your application
> doesn't require comparable addresses, go for strings
>
------------------------------------------------------------------------------
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