Re: IPv6 address parsing
Michael Powell <[email protected]>
| Newsgroups | gmane.comp.parsers.spirit.general |
|---|---|
| Message-ID | <CAMEoF_EB5ZbECEyDm7=RCW88da9ERFo_AuFrsavaryJvrYBF=A@mail.gmail.com> |
On Thu, Dec 7, 2017 at 12:07 PM, Seth <[email protected]> wrote: > On 07-12-17 17:35, Michael Powell wrote: >> How about in the scope of an IPv6 address? > > Your choice again. Exactly the same is at play. There are many valid > representations of the same IPV6 address. This is why I asked: > > On 07-12-17 08:31, Seth wrote: >> Parsing, or just validating? I remember from last time (when you were >> doing ipv4) you weren't interested in interpreting the data at all, just >> validating some string input formats? Well, you remembered incorrectly. I never said just validating. I want to parse for use. So again, from an pseudo attribution grammatical perspective, this is doable? Inclusive of port number: string >> -(uint8_t >> uint8_t >> uint8_t >> uint8_t) >> uint16_t >> eoi. Ultimately, I just want: string >> uint16_t >> eoi. If there's a doable intermediate step of parsed individual octets, so be it; no problem. Thanks! Cheers, Michael ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot