Eric In case You are not already aware of it, I would like to point You to my ABNF parser generator, abnfc, (most RFCs are specified using ABNF)
https://github.com/nygge/abnfc The documentation is nonexistent, but it was presented at EUC 2008 http://www.erlang.org/euc/08/1500Nygren2.pdf There has been some changes after that, so contact me if You have any questions/problems. In general I am not sure it is a good idea to put all RFC parsers in one erlang application. Since after a while You may get a large number of unrelated stuff. But on the other hand many RFCs imports parts of other RFCs so I do not have any good ideas on how to structure it. Maybe the best is just to make a big bag of parsers and let people pick the ones they need. /Anders On Wed, Oct 5, 2011 at 10:48 AM, Eric Merritt <[email protected]> wrote: > Hello All, > > I have started an RFC parsing library in support of my latest > endeavor. This seems like a target to put under erlware. I thought I > would float the idea to the list. > > https://github.com/ericbmerritt/erfc_parsers > > I dont have a specific goal of implementing all RFCs but as I need > them (RFC 821 should show up shortly) I will add them. > > What does everone think of putting them under erlware? > > Eric > > -- > You received this message because you are subscribed to the Google Groups > "erlware-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/erlware-dev?hl=en. > > -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
