Earlier quoted context omitted.
AFAIK none of the TLDs allow for MX records on just the TLD i.e. johndoe@com will never exist
I'm not on about gTLDs like .com, I'm on about the privately owned ones like .amazon and .google
Show HN: Regex Cheatsheet
131–135 of 135 posts
Re: Show HN: Regex Cheatsheet
#132Earlier quoted context omitted.
Oddly, lookbehinds are evil only in a specific backtracking world. We never got around to implementing arbitrary lookarounds in Hyperscan ( https://github.com/intel/hyperscan ) but if we had done something in the automata world to handle lookaround, lookbehinds are way easier than lookaheads. To handle a lookbehind, you really only need to occasionally 'AND' together some states (not an operation you would normally d…
Even for non-fixed length expressions?
Re: Show HN: Regex Cheatsheet
#133I used to use this site http://txt2re.com which is now off the grid, at the least since yesterday. :( Unlike most regex helpers, in this one you would start with the text you want to filter/parse and then it would suggest you possible extractions. Do you know any alternatives?
Re: Show HN: Regex Cheatsheet
#134Earlier quoted context omitted.
I'm not on about gTLDs like .com, I'm on about the privately owned ones like .amazon and .google
I didn't say gTLDs. The id est applies to all.
Re: Show HN: Regex Cheatsheet
#135Earlier quoted context omitted.
boom. https://regex101.com/r/PxSY4U/1 technically it does parse it. :P
Nope. bar">My First Heading will misparse. (This is valid HTML 5.) You really need recursive regex or something equivalent in power, otherwise you will always fail.