Date: Sun, 28 Jun 2009 22:51:29 -0400 From: "Aryeh M. Friedman" <aryeh.friedman@gmail.com> To: Glen Barber <glen.j.barber@gmail.com> Cc: Vince Sabio <vince@vjs.org>, freebsd-questions@freebsd.org Subject: Re: what character is a physical newline Message-ID: <4A482C31.6070600@gmail.com> In-Reply-To: <4ad871310906281946g7ed9c1d6m477fd3dfecc8d330@mail.gmail.com> References: <4A48252C.1090808@gmail.com> <4ad871310906281926i54fdac53u1d4681c8060e4d36@mail.gmail.com> <4A4826A5.6020506@gmail.com> <4ad871310906281930k644b5d5fnf448decf8e489c4c@mail.gmail.com> <p05200f50c66dd8cc3cd7@192.168.5.248> <4ad871310906281946g7ed9c1d6m477fd3dfecc8d330@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Just incase you guys are curious the reason for doing the parser from
scratch is it is designed to lex/parse families of languages not just a
single lang for example (there is very large overlap between
c/c++/java/c#/etc. as there is in the tag langs like XML/HTML)... also
generators produce unreadable code (and impossible to hand modify if
you're not quite happy with the generated code) thus I refer to the
design as a heiractical recursive decent parser (i.e. it lexs/parses the
commonalties of a family [or set of families {all ascii vs, unicode
langs for example are a set of families} before it attempts to handle
the actual lang [or family in the case of set of families]).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A482C31.6070600>