[BinaryPHP-devel] Pre-Release requisite

[Derek F. <sha...@as...>]

Before we event think of releasing an rc, we should concentrate on 
finishing a few things completely. Here is my completely inaccurate list.

I. parser.
   a. error handling
   b. references?
   c. loops
           1) for
           3) foreach
           2) while
   d. control mechanisms for functions that have yet to be added. added 
to the error handler; E_INCOMPLETE. We should also keep in mind the 
major changes being done to        php at the moment. As deprecated 
functionality is being removed, we shouldn't touch it at all. Let's 
leave deprecated functionality _gone_. As for E_STRICT catches,         
        believe it would be best to just make (i know i'm a bastard for 
this) bad code call "good functions" internally. ala no bar, if someone 
uses bar() make it call foo() internally,         because foo() is 
faster, less resource extensive, whatever.

II. Functions and constructs
    a. output buffering(?)
    b. all datatype operation functionality. (save objects, of course, 
_daeken_ ;)   )
    c. constructs... we must test _everything_.

III. Extensions
    a. MySQL finished? (I could tackle this. I want to rewrite Hexus' 
code, no offense Hexus! It would just be easier for me to write further 
if it was all my code. )
          1) there are going to be some licensing issues with this 
one... We'll need to get word from and to the MySQL co.
    b SQLite? SQLii?
          1) Might run into trouble with the SQLite team....
    c. Sockets?
          1) there are a lot of obscure but important functions that 
need to be done with this...
    d. Streams?
          2) I don't even want to think about this section, heh.


This is wholly incomplete, I know... Lets get an idea of what we need 
and get a list done. Also, we need a few things done as far as project 
management goes...

1) management system for functions complete/incomplete, with notes and a 
way to mark things complete/incomplete/bug ridden, etc, with feedback.
2) bug manager.
3) documentation documentation documentation! I would concentrate on 
getting the first two things done before we worry about this, though. We 
all love api documentation, I know, but please, contain yourselves.... ^_~
The first two entail a website of some form, I doubt a wiki is going to 
suffice for long...