Re: [Opencxx-users] Re: [Synopsis-devel] The Array type

[<se...@in...>]

On Sun, 2004-08-01 at 14:17, Stefan Seefeld wrote:
> Hi Gilles,
> 
> Gilles J. Seguin wrote:

[...]

> > Next project in opencxx, increase test coverage.
> > Any idea are welcome.
> 
> I'm doing that inside synopsis right now, i.e. I'm adding
> tests to the opencxx backend inside synopsis. My tests are
> all organized using the qmtest framework (www.qmtest.com),
> and I offered Grzegorz to put something similar into place
> for his project.

QMtest is a very god choice. QMtest is a general-purpose,
cross-platform software testing tools. It also have a gui
for creating, managing, and executing tests through a browser,
provides support for parallel test execution.

The first goal will be to provide a 'make test' target, that
is intended for developer, which increase the level of
confidence that changes are not affecting others functionalities
in an non intended way.  We will still provide a 'make check'
target that is generally done after ./configure && 'make',
to ensure functionality before performing 'make install'.

Stephan could you give me access to what you have already done.
Or things, sorry for my English, that can be done now.

We need to discuss what needs to be part of opencxx or synopsis.
And prioritization of work step.

> That being said, I still hope (as you may know) that we can at some
> point merge both projects. Right now I'm doing most work on synopsis,
> offering from time to time to merge back fixes into the OpenC++ project.
> 
> > The main point of this email, how can I see the work that
> > you are doing on the C++ parser.
> > I have done 'svn checkout', so I have revision 1332.
> 
> I'm just starting my work on the backend. My plans are (in that order):
> 
> * rewrite some low level classes (Buffer, Lexer, basically)
> 
> * make the existing API more clean (const-correct, more typed, etc.)
> 
> * try to understand how the Parser needs to be changed in order to
>    correctly understand the tokens, i.e. build a correct parse tree / AST
>    (see recent posts on the opencxx list).
> 
> * build a true high-level AST API on top (no more Car() / Cdr() calls !)
> 
> * export that AST API publicly through C++ as well as python
> 
> * get rid of the occ executable, provide a python script instead (for
>    backward compatibility only)
> 
> * solidify the C++ / python APIs to let users build their domain-specific
>    applications either as python scripts or C++ programs
> 
> I realize this is a lot of work. I'm not sure what the timeframe is to get
> all of this done. I'v almost finished the first point (the Buffer is committed,
> the Lexer will follow one of these days).
> If you are interested in getting involved, let me know.
> 
> Kind regards,
> 		Stefan