This is what I can think of for a concrete todo before the beta...
http://www.php.net/~sterling/php5/BETA
any thing i missed? anything extraeneous?
-Sterling
"Nothing is particularly hard if you divide it into small jobs."
- Henry Ford
Actually I'm working on the php5 version of ext/java extension :)
Moriyoshi
Sterling Hughes sterling@bumblebury.com wrote:
This is what I can think of for a concrete todo before the beta...
http://www.php.net/~sterling/php5/BETA
any thing i missed? anything extraeneous?
We also need to sort out the mbstring license mess. We cannot distribute
code that is under the LGPL and modified by us. The relevant clauses from
the LGPL:
-
You may modify your copy or copies of the Library or any portion of
it, thus forming a work based on the Library, and copy and distribute such
modifications or work under the terms of Section 1 above, provided
that you also meet all of these conditions:a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no charge
to all third parties under the terms of this License.
...
We do not meet a) and c) here. Specifically mbregex and mbfilter* have
this problem. The code in them is under the LGPL and we have modified
these files.
Now, if we found a way around putting modifications directly into these
files and simply wrapped them transparently, then we are ok as per this
clause in the LGPL:
- You may copy and distribute verbatim copies of the Library's complete
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty; and
distribute a copy of this License along with the Library.
The other option if a transparent wrapper can't be done is to get the
permission of the authors to distribute these files under the PHP license.
-Rasmus
I've added the mb stuff to the list.
Can the extension itself be considered a complete work? Therefore by
distributing the extension (under the LGPL) without modifications with
PHP, we essentially keep the cancer isolated?
-Sterling
We also need to sort out the mbstring license mess. We cannot distribute
code that is under the LGPL and modified by us. The relevant clauses from
the LGPL:
You may modify your copy or copies of the Library or any portion of
it, thus forming a work based on the Library, and copy and distribute such
modifications or work under the terms of Section 1 above, provided
that you also meet all of these conditions:a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no charge
to all third parties under the terms of this License.
...We do not meet a) and c) here. Specifically mbregex and mbfilter* have
this problem. The code in them is under the LGPL and we have modified
these files.Now, if we found a way around putting modifications directly into these
files and simply wrapped them transparently, then we are ok as per this
clause in the LGPL:
- You may copy and distribute verbatim copies of the Library's complete
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty; and
distribute a copy of this License along with the Library.The other option if a transparent wrapper can't be done is to get the
permission of the authors to distribute these files under the PHP license.-Rasmus
--
"Programming today is a race between software engineers stirring to
build bigger and better idiot-proof programs, and the universe trying
to produce bigger and better idiots. So far, the universe is winning."
- Unknown
I've added the mb stuff to the list.
Can the extension itself be considered a complete work? Therefore by
distributing the extension (under the LGPL) without modifications with
PHP, we essentially keep the cancer isolated?
We would have to argue that the extension is a "software library". Which
in a sense it is I guess.
-Rasmus
Sure. PECL is a proof of that. ;-)
-Sterling
I've added the mb stuff to the list.
Can the extension itself be considered a complete work? Therefore by
distributing the extension (under the LGPL) without modifications with
PHP, we essentially keep the cancer isolated?We would have to argue that the extension is a "software library". Which
in a sense it is I guess.-Rasmus
--
"C makes it easy to shoot yourself in the foot; C++ makes it harder,
but when you do, it blows away your whole leg."
- Bjarne Stroustrup
At 03:46 PM 6/19/2003 +0200, Marcus Börger wrote:
Hello Sterling,
We need exceptions instead of errors whenever a try/catch block is
entered or a constructor gets called. This is a very easy thing to
implement but we need a consensus before doing so.
You can always throw the exception manually in the constructor. The bottom
line is that right now no one seems to have the answer on what should be
done without making a complete mess out of the error/exception handling in
PHP. I suggest that in the meanwhile we keep things the way they are, get
the beta out the door and see what feedbacks we get and what catches on
strongly in the dev community.
p.s.: And i'd still like to have final classes
No big deal IMO and not necessary for the beta.
Andi
At 08:15 PM 6/18/2003 -0400, Sterling Hughes wrote:
This is what I can think of for a concrete todo before the beta...
http://www.php.net/~sterling/php5/BETA
any thing i missed? anything extraeneous?
These are very small tasks. I suggest we assign owners to each and aim for
the 30th of June for wrapping up a Beta.
Do we have volunteers?
Andi
On Thu, 19 Jun 2003 2:15:06 +0200, Sterling Hughes wrote
(in message 1055981706.8233.10.camel@hasele):
This is what I can think of for a concrete todo before the beta...
http://www.php.net/~sterling/php5/BETA
any thing i missed? anything extraeneous?
-Sterling
how about bug #21669? can cause big troubles...
At 01:32 AM 6/22/2003 +0200, Terje Torkelsen wrote:
On Thu, 19 Jun 2003 2:15:06 +0200, Sterling Hughes wrote
(in message 1055981706.8233.10.camel@hasele):This is what I can think of for a concrete todo before the beta...
http://www.php.net/~sterling/php5/BETA
any thing i missed? anything extraeneous?
-Sterling
how about bug #21669? can cause big troubles...
I'll try and take a look at this one.
Andi
At 02:32 22/06/2003, Terje Torkelsen wrote:
On Thu, 19 Jun 2003 2:15:06 +0200, Sterling Hughes wrote
(in message 1055981706.8233.10.camel@hasele):This is what I can think of for a concrete todo before the beta...
http://www.php.net/~sterling/php5/BETA
any thing i missed? anything extraeneous?
-Sterling
how about bug #21669? can cause big troubles...
It's fixed!
Zeev
On Sun, 22 Jun 2003 13:00:23 +0200, Zeev Suraski wrote
(in message 5.1.0.14.2.20030622140018.0a9792a0@localhost):
At 02:32 22/06/2003, Terje Torkelsen wrote:
On Thu, 19 Jun 2003 2:15:06 +0200, Sterling Hughes wrote
(in message 1055981706.8233.10.camel@hasele):This is what I can think of for a concrete todo before the beta...
http://www.php.net/~sterling/php5/BETA
any thing i missed? anything extraeneous?
-Sterling
how about bug #21669? can cause big troubles...
It's fixed!
Zeev
nice! works perfect so far.