I also reached out to them on Twitter but they directed me to this form. I followed up with them on Twitter with what happened in this screenshot but they are now ignoring me.

  • laurelraven@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    11 months ago

    What claim, that I probably could? I didn’t say anything at all about it being easy, it would be a pain in the ass and involve a lot of checking the RFC, but I could probably make one that accurately represents the spec if I wanted to take the time, and even then I’m not exactly confident I would hit every edge case.

    But why would I go to that hassle when there are well designed and vetted ones available?

    I believe you missed the point I was making

    • nybble41@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 months ago

      The full email address syntax described in the RFC cannot be precisely matched with a mere regular expression due to the support for nested comments. The need to track arbitrarily deep nesting state makes it a non-regular language.

      If you remove the comments first the remainder can be parsed with a very complex regex, but it will be about a kilobyte long.

    • elephantium@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      when there are well designed and vetted ones available?

      I’m not convinced of this, tbh. IIRC the RFC can’t be described in a regex at all.