Re: [boost] GSoC 2010 - Boost.Phoenix

Subject: Re: [boost] GSoC 2010 - Boost.Phoenix
From: Thomas Heller (thom.heller_at_[hidden])
Date: 2010-03-21 03:56:20

On Sunday 21 March 2010 04:06:25 Joel de Guzman wrote:
> On 3/21/2010 1:07 AM, joel falcou wrote:
> > Thomas Heller wrote:
> >> Hi Joel,
> >> 
> >> Thank you for the wiki url. I will dive into that.
> >> Some general questions:
> >> - The interface should be (more or less) the same as phoenix V2?
> > 
> > It has to be the same to minimize disruption. If anythign need to be
> > changed for accomodating
> > some inenr changes, it'll have to be discussed.
> > 
> >> - The main extention point for a user should be phoenix::functions?
> > 
> > we wanted to have more extension scenario, like simplifying how to make
> > new actor (like let's say I want to add new control structure
> > or new palceholder-like actor with special member). The problem is in
> > fact hidign proto internals in a pretty way so user wntign to extend
> > don't have to master Proto.
> > 
> >> - What exactly to you want to have in the proposal? function/class
> >> interfaces?
> >> general description of phoenix?
> > 
> > Good question. Let's see what Joel or Harmut have to say on the matter.
> 
> To be honest, I am not entilrely sure I understand the question.
> Perhaps I lost the context here. Could you elaborate? Do you mean
> to ask about the scope of the proposal?

Let me try to rephrase one part of my question.
What do you expect from me as a GSoC Student?

I think I read through all the previous discussions, articles and 
documentation about phoenix and proto.
Let me try to sum everything up:
  - Some basic building blocks (actors, statements?, functions?, ...)
  - Easy extendable without exposing to much proto specific stuff
I hope i got that right, more or less.

Right now i am waiting to take a look at Joel's (Falcou) prototypes to get 
some more insights on what you already have done.

The other part of my question was more like: What should be actually put into 
the formal proposal. Just an overall description? Something like pseudo/C++ 
interfaces and/or first implementation ideas?

Regards,

   Thomas