Re: [pygccxml-development] Future of pypp_api...

[Lakin W. <lak...@gm...>]

On 8/20/06, Allen Bierbaum <al...@vr...> wrote:
>
> Roman Yakovenko wrote:
> > That is what I am asking you for. Py++ solves real problems and
> > exports real projects.
> > Please be specific.
>
> The specifics in this case are not going to help much because there is a
> bigger question which has to be answered in order to evaluate the
> specifics.  That question is what is Py++ going to provide for a *user*
> api (note: not the developer API)?
>
> Will it be:
>    a) A set of classes and interfaces to write code generators
> or
>    b) A simple and complete domain specific language that makes the
> simple things simple and the hard things possible (by using the class
> interfaces behind the scenes)
>
> The reason I am not giving specifics is because they don't matter if
> what you want is A and what I want is B.  To me pypp_api is a better
> solution for providing b.  It has shortcomings but those can be
> eliminated.


I don't think that these options are mutually exclusive.  You also make it
sound like the second option is  the only option which can provide
simplicity.  I disagree.  There are plenty of situations where the first
option can "make the simple things simple and the hard things possible."  So
why is it that you think providing a domain specific language is the only
way to provide a simple solution to user's problems?

As per my previous email, I think specifics here are essential.  What is it
about the py++ api that makes simple things _not_ simple?   Given a concrete
set of issues, Roman, you, Matthias and the rest of us can work towards
addressing these issues.

I think that Roman would agree that he wants to provide a solution which is
as simple as possible for simple things, and still makes the hard things
possible. In order to do this, he needs to know what is wrong with the
current situation.

Lakin