It was thus said that the Great Petite Abeille once stated: > > On Dec 27, 2020, at 00:52, Sean Conner <sean at conman.org> wrote: > > > > "Perfect is the enemy of good." > > Agree. My own parserss are on the pragmatic side of the spectrum (even > though path segments are preserved, as I tend to use databases rather than > file systems). How do you preseve them? As the encoded "%2F"? Do you convert the encoded values to uppercase? Lowercase? Keep them the same? > I was hoping you where a better person that I'm, to borrow > your own line. But you said it yourself, you fall on the pragmatic side. > I suspect I should stop hoping for a full-fledge LPEG grammar for MIME > emerging from Conman's lab :/ Well, I do have one [1], although I'm not sure how "full-fledged" it is. I also lowercase the actual MIME type (so "TEXT/PLAIN" will become "text/plain") to make it easier to use the results. I even have one for email [2], which can even parse RFC-822 style email addresses [3], but I'm rethinking how I parse Internet messages as I'm not entirely happy with my current approach. > Oh well. We are all flawed. Skynet will just crash and segfault. > > No one cares. Even on a mailing list dedicated to designing a protocol, > one ends up being "pedantic". > > I now fell the same rage-quit as bie. > > On the plus side, next time someone dare to mention any RFCs, just punch > them in the face. Life is too short. Life is too short to follow the WhatWG "standard" [4], so I guess it's a "pick your poison" type situtation. > Let's stop pretending. Yeah, let's roll our own crypto and addressing scheme! What can possibly go wrong? -spc [1] https://github.com/spc476/LPeg-Parsers/blob/master/mimetype.lua [2] https://github.com/spc476/LPeg-Parsers/blob/master/email.lua [3] Muhammed.(I am the greatest) Ali @(the)Vegas.WBA [4] https://url.spec.whatwg.org/#concept-url-parser
---
Previous in thread (105 of 109): 🗣️ Sean Conner (sean (a) conman.org)
Next in thread (107 of 109): 🗣️ Petite Abeille (petite.abeille (a) gmail.com)