Since Martin dropped my idea here, perhaps I should explain myself a bit more...
I think that Pike is a very pleasent language with lots of features. Most of the time, missing features are added as needed. This has worked fairly well (and still does).
The problem as I see it, is that it is hard for people (outside of Linköping) to know what to work towards. I feel that we need to structure our efforts a bit so that everyone will know the major goals for the next release. There are plenty of good coders on this list and many of us could pitch in a few lines on one of the goals instead of developing some personal project.
I would like to see some discussion here about the goals. I want to keep the discussion about what should and shouldn't be set as a goal on this list and once a goal has been set, it should be stated on the pike-site.
Once the goals are put on the Pike-site, I would also like to see that each goal gets a more detailed description. Take the suggested goal "embeddable" for example. There was a discussion about it a few weeks ago. It would be nice to have a page with pros and cons of different solutions, pointers to interesting reading etc. Of course, it is possible to search the mailarchive every time, but wouldn't it be practical to document stuff on a webpage to and keep the list for discussions? When I was in Linköping a week ago, I discussed ways of making Pike embeddable with Martin and he suggested a very simple scheme for a first version. That would be perfect to put on a page as a startingpoint for someone to try.
/ Marcus Agehall (Scanian)
Previous text:
2004-05-06 06:06: Subject: Re: Pike 7.6
Marcus Agehall suggested that we should write a "feature plan" or something like that and put it on the webpage. My views for the next version of Pike (which I suggest be 8.0):
- Embeddable.
- Easy to build on windows.
- Smaller.
- Documented and "stable" C interface.
/ Martin Nilsson (räfsfiskal)