On Tue, Oct 21, 2008 at 08:45:11AM -0700, David Fetter wrote:
> > As against that ... does a2p produce code that is
> > readable/maintainable?
>
> Not that I've seen. There are modules on CPAN (I know, I know) for
> dealing with lexx and yacc, and those are probably better for the
> purpose.
Wel
On Tue, Oct 21, 2008 at 08:31:54AM -0400, Tom Lane wrote:
> So it's all pretty messy and neither choice is exactly desirable. I
> think maintaining parallel versions of an ecpg parser generator
> would be no fun at all, though, so the perl choice seems more or
> less forced. We could either pres
Michael Meskes <[EMAIL PROTECTED]> writes:
> ... The only manual work I see in the
> future is adding some special ecpg handling. I fully expect this script to
> generate a working parser for every single change in gram.y. However, if some
> new rule needs a different aka non-default handling in ec
I share Tom's thoughts completely. My personal goal is definitely to make ecpg
parser generation a fully automated task. The only manual work I see in the
future is adding some special ecpg handling. I fully expect this script to
generate a working parser for every single change in gram.y. However,
Mike Aubury <[EMAIL PROTECTED]> writes:
> In reality - it doesn't look too disimilar from the awk original. I didn't
> appreciate that we'd probably need to keep 2 versions (one for unix and one
> for windows). In that case - I'd argue that we only need to "maintain" one
> and regenerate the oth
Perl code thats readable and maintainable ;-)
In reality - it doesn't look too disimilar from the awk original. I didn't
appreciate that we'd probably need to keep 2 versions (one for unix and one
for windows). In that case - I'd argue that we only need to "maintain" one
and regenerate the oth
Mike Aubury <[EMAIL PROTECTED]> writes:
> Also - for completeness (for the list) - I think the plan is to convert the
> awk to perl (via a2p + some tweaking) if awk is not already used as part of
> the build process (to avoid adding another prerequisite..)
Hmm. I believe the current state of p
> (Mike, it lacks a copyright notice, I take it BSD is okay).
Thats fine with me..
Also - for completeness (for the list) - I think the plan is to convert the
awk to perl (via a2p + some tweaking) if awk is not already used as part of
the build process (to avoid adding another prerequisite..)
