Dear PHP users,
PHP 5.0.0 Beta 3 has been released. Many bugs have been fixed since Beta 2,
some of which aren't mentioned in the NEWS file (which you can find at the
end of this email).
The PHP 5.0 source tree will now enter a feature freeze and we are moving
into bug fixing mode, therefore,
Hi,
There's going to be zero public testing of this extension when people
need to:
1) Install BitKeeper (which I can't even do on my Mac OS X)
2) Upgrade to autoconf 2.5.3
3) Upgrade to Automake 1.5
4) Upgrade to Libtool 1.4
5) Upgrade to Bison 1.7.5
If they want to build MySQL 4.1
On Thu, 13 Nov 2003, Georg Richter wrote:
There was already a feature freeze for 4.1.x, but on Internal Developer
Meeting this week in Bordeaux we decided to add 2 more functions for multi
query support and profiling. When this is done (Monty told me to add it this
week) packaging for the new
On Nov 12, 2003, at 16:14, Olivier Hill wrote:
Wez Furlong wrote:
That would be illegal.
Yup.. unless PHP would be OSI certified?
Version 3 of the PHP license is OSI certified now. :)
Or have a license exception from MySQL, which is slow to obtain.
The license exception is being reviewed by the
2. session support for internal classes. should we have a
Serializable
interface which classes inherit, or have sleep and wakeup
handlers in the zend_object_handlers structure ?
I guess it's possible. In most cases I think internal classes won't be
serialized though, such as
At 11:03 AM 11/13/2003 +, Wez Furlong wrote:
2. session support for internal classes. should we have a
Serializable
interface which classes inherit, or have sleep and wakeup
handlers in the zend_object_handlers structure ?
I guess it's possible. In most cases I think
Guys (n' Girls),
I think there was a lot of good and positive talk in the past few emails.
Let me summarize:
a) There are still people who have to fix some of their extension and are
actually working on them. These fixes should definitely be in PHP 5 and the RC.
b) There are people who are
Andi Gutmans wrote:
It's not as if the Java one is a very feasible extension to use in
production environments because it's slooo and heavy.
I agree. But I think people might yell at us because when remove
functionality from PHP 4 to PHP 5.
--
Sebastian Bergmann
On Wed, 2003-11-12 at 08:57, Sebastian Bergmann wrote:
Andi Gutmans wrote:
It's not as if the Java one is a very feasible extension to use in
production environments because it's slooo and heavy.
I agree. But I think people might yell at us because when remove
functionality
On Wed, 12 Nov 2003, Sebastian Bergmann wrote:
Andi Gutmans wrote:
It's not as if the Java one is a very feasible extension to use in
production environments because it's slooo and heavy.
I agree. But I think people might yell at us because when remove
functionality from PHP 4 to
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Hi Derek,
I would suggest starting a mailing list or some such for the
admins of php community websites, where you guys can write up
small explanations and lists of your changes that make it to cvs.
started this one
On Nov 12, 2003, at 3:42 AM, Stig S. Bakken wrote:
On Wed, 2003-11-12 at 08:57, Sebastian Bergmann wrote:
Andi Gutmans wrote:
It's not as if the Java one is a very feasible extension to use in
production environments because it's slooo and heavy.
I agree. But I think people might yell
On Wed, 12 Nov 2003, Andi Gutmans wrote:
So I suggest the following, let's kick ourselves in the tush, aim for Beta
3 on the 30th of November, and hopefully after that we can do a feature
freeze and go into bug fixing only mode. We can re-evaluate this date as we
get closer in case people are
That would be illegal.
If we're rushing to release, can we at least bundle a version of
mysqli that can work with the 4.1-alpha download packages on
MySQL.com?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
At 12:22 AM 11/13/2003 -0500, l0t3k wrote:
Two things that need fixing :
1. support for class constants for internal classes. Christiano has
already posted a patch.
I applied his patch. As I told him I don't think persistent internal
classes across requests will be supported with all the
15 matches
Mail list logo
