Re: [ANN] an EBNF parser and coding pattern tool (LGPL)

[codeworker@free.fr (Cedric LEMAIRE)]

> > codeworker@free.fr (Cedric LEMAIRE) wrote:
> > You must write the Extended BNF of the language you use (I don't
> > propose EBNF for languages yet) and to redefine some clauses
> > (identifier of a variable that is being declared, lambda-expression,
> > method identifier) to apply/remove the Hungary Notation on it.
> >
> anthony.williams@anthonyw.cjb.net wrote:
> So, if you want to use CodeWorker to modify C++ code based on a set of rules,
> you need a grammar for C++, which you don't supply :-(

CodeWorker is Open-Source and, in that spirit, each contribution of
interested people that might improve the tool is welcome. For the C++
grammar, I'm taking it in charge finally.

> I can see the benefit of this tool, in that it would allow you to use
> Aspect-Orientated Programming in C++ by performing C++-to-C++ translations
> based on a set of rules, but someone has to write the grammar first.

This tools pretents first generating a lot of code for you, acquiring
your Design from any kind of format (I'm rewriting the Rational ROSE
one for publishing it, the first I wrote isn't my intellectual
property) - thanks to the E-BNF -, decorating the parse tree and
exploring it through coding patterns. The process is straight-forward,
without a binding to an external programming language, as proposed
ordinarly.

The source-to-source translation came later (I wrote a LaTex-to-HTML
translation adapted to my documentation for example). It isn't the
original purpose of the tool ; it explains why no language grammars
are available yet!

> C++ is not an easy language to parse, so I don't fancy that job.

I understand. I wrote the E-BNF grammar of the C++/ISO 14882 ; It
scans C++ files. I need more time to give a description of all
declarations seen from any scope in the C++ file.
I terminate this tedious job as soon as possible.

--Cedric
-- 
comp.lang.c.moderated - moderation address: clcm@plethora.net