Hello Andi,
Tuesday, November 11, 2003, 10:23:59 PM, you wrote:
[...]
> I also don't think we should be waiting for new extensions like PDO. It is
> impossible to synchronize with every extension out there. PDO sounds like
> it'll be something really useful, and when it's ready and useful enough
Stig S. Bakken wrote:
> John has a very good point in that some of the changes that people
> are looking to PHP 5 for will be extension specific, releasing an
> RC before the extensions are more or less stable doesn't make sense
> to me.
Also do not forget that PHP 5 currently lacks extensions t
Forgive me for the shameless plug, but since I work for the company who
owns the site I couldn't help but throw in you can always post the new
articles about PHP5 here:
www.devpapers.com
Jeremy
On Wed, 2003-11-12 at 06:15, Kevin Waterson wrote:
> This one time, at band camp, "Wolfgang Drews" <[E
Edin Kadribasic wrote:
This was entirely my fault. Any chance of getting an updated diff? And I
promise it will it will not be overlooked this time :)
I don't blame anyone, I just though the patch wasn't welcome.
If you can wait until next Saturday, I'll do my magic again (not
really... maybe mo
On Wednesday, Nov 12, 2003, at 02:21 Europe/Copenhagen, Olivier Hill
wrote:
Edin Kadribasic wrote:
Some major win32 build issues that need to be dealt with before RC1:
1. php4 -> php5 rename
I've submitted different .dsp/.dsw files to fix this problem, and I
even posted a diff file to do the sam
Edin Kadribasic wrote:
Some major win32 build issues that need to be dealt with before RC1:
1. php4 -> php5 rename
I've submitted different .dsp/.dsw files to fix this problem, and I even
posted a diff file to do the same job. No one responded and no one
commited it.
Oliver
--
GB/E/IT d+ s+:+ a
This one time, at band camp, "Wolfgang Drews" <[EMAIL PROTECTED]> wrote:
> *This message was transferred with a trial version of CommuniGate(tm) Pro*
> > I agree. I think we need to take care of this. I wouldn't count
> > on any one
> > company for this (although this is also important).
> > How
This one time, at band camp, "Wolfgang Drews" <[EMAIL PROTECTED]> wrote:
> *This message was transferred with a trial version of CommuniGate(tm) Pro*
> > I agree. I think we need to take care of this. I wouldn't count
> > on any one
> > company for this (although this is also important).
> > How
On Tuesday, Nov 11, 2003, at 19:05 Europe/Copenhagen, Andi Gutmans
wrote:
Hey guys,
I think the PHP 5 tree has matured a lot and it's time to release an
RC. I think end of November or mid-December makes sense. I'd like to
aim at the former date.
Are there any major (as in "major") issues which
Derick Rethans wrote:
On Tue, 11 Nov 2003, Shane Caraveo wrote:
Adam Maccabee Trachtenberg wrote:
On Tue, 11 Nov 2003, John Coggeshall wrote:
I know Shane was working on some major improvements to simplexml that I
don't know if he's finished yet. Sterling didn't seem to have any
interest in
Sorry to interject, but shouldn't the feature set be frozen before
moving to a release candidate? This stage should mean to people that
they can start building software on the new system because all the
features are fixed and are not going to change, even though the system
may still have bugs a
On Tue, 11 Nov 2003, Shane Caraveo wrote:
> Adam Maccabee Trachtenberg wrote:
>
> > On Tue, 11 Nov 2003, John Coggeshall wrote:
> >
> >
> >>I know Shane was working on some major improvements to simplexml that I
> >>don't know if he's finished yet. Sterling didn't seem to have any
> >>interest
Yes, but it's not only the engine that would be going into RC, it's the
entire distribution.
John has a very good point in that some of the changes that people are
looking to PHP 5 for will be extension specific, releasing an RC before
the extensions are more or less stable doesn't make sense to m
John Coggeshall wrote:
To be honest, I think the answer is somewhere in the middle. Basically, the
engine is done. I think the XML extensions and SQLite are pretty mature,
I know Shane was working on some major improvements to simplexml that I
don't know if he's finished yet. Sterling didn't s
Adam Maccabee Trachtenberg wrote:
On Tue, 11 Nov 2003, John Coggeshall wrote:
I know Shane was working on some major improvements to simplexml that I
don't know if he's finished yet. Sterling didn't seem to have any
interest in really finishing the code he did write from our
conversations.
I k
On Tue, 11 Nov 2003, John Coggeshall wrote:
> I know Shane was working on some major improvements to simplexml that I
> don't know if he's finished yet. Sterling didn't seem to have any
> interest in really finishing the code he did write from our
> conversations.
I know that Shane is also portin
Thank you for sending patch.
I applied your first patch to cvs, but, the second change
was already applied in cvs.
Rui
On Tue, 11 Nov 2003 15:45:35 +
Joe Orton <[EMAIL PROTECTED]> wrote:
> 4.3/ext/mbstring/mbstring.c: In function `php_mb_gpc_encoding_converter':
> 4.3/ext/mbstring/mbstring
Oh, and let's not forget Pierre's PIMP extension -- anyone who has seen
his code/slides knows that it blows GD out of the water and he's still
cleaning things up there too.
John
On Tue, 2003-11-11 at 17:03, John Coggeshall wrote:
> > To be honest, I think the answer is somewhere in the middle. B
*This message was transferred with a trial version of CommuniGate(tm) Pro*
> I agree. I think we need to take care of this. I wouldn't count
> on any one
> company for this (although this is also important).
> How about the people from internals@ who made changes volunteer to write
> about their
> To be honest, I think the answer is somewhere in the middle. Basically, the
> engine is done. I think the XML extensions and SQLite are pretty mature,
I know Shane was working on some major improvements to simplexml that I
don't know if he's finished yet. Sterling didn't seem to have any
inter
At 10:39 PM 11/11/2003 +0100, Wolfgang Drews wrote:
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Hi,
> I think the PHP 5 tree has matured a lot and it's time to release
> an RC. I
> think end of November or mid-December makes sense. I'd like to aim at the
> former date
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Hi,
> I think the PHP 5 tree has matured a lot and it's time to release
> an RC. I
> think end of November or mid-December makes sense. I'd like to aim at the
> former date.
> Are there any major (as in "major") issues whic
Hi all,
I guess I found a bug at "zend_compile.c". IMHO when you want to create
an internal hashtable, that will be filled with internal zvals
(malloc'ed instead of emalloc'ed), you should pass the "internal zval
destructor" to the hashtable initialization function. Currently,
"zend_compile.c" use
I went over this list today. Some need to be addressed but the majority are
not engine problems.
I suggest everyone here takes a look at them and tries to solve what they can.
I have already planned time to go over the engine ones.
Andi
At 04:29 PM 11/11/2003 -0500, Ilia Alshanetsky wrote:
Andi,
At 10:08 PM 11/11/2003 +0100, Thies C. Arntzen wrote:
On Tue, Nov 11, 2003 at 10:01:32PM +0100, Stig S. Bakken wrote:
> On Tue, 2003-11-11 at 19:05, Andi Gutmans wrote:
> > Hey guys,
> >
> > I think the PHP 5 tree has matured a lot and it's time to release an
RC. I
> > think end of November or mid
Andi,
According to:
http://bugs.php.net/search.php?cmd=display&bug_ntype[]=Feature%2FChange+Request&bug_ntype[]=Documentation+problem&bug_ntype[]=PECL+related&bug_ntype[]=PHP-GTK+related&bug_ntype[]=Website+problem&status=Open&search_for=&php_os=&boolean=0&author_email=&bug_age=0&by=&order_by=id&d
At 09:56 PM 11/11/2003 +0100, Georg Richter wrote:
> I think the PHP 5 tree has matured a lot and it's time to release an RC. I
> think end of November or mid-December makes sense. I'd like to aim at the
> former date.
thats too fast, or do you mean Nov/Dec. 2004? Why such a hurry? Shouldn't we
hav
On Tue, Nov 11, 2003 at 10:01:32PM +0100, Stig S. Bakken wrote:
> On Tue, 2003-11-11 at 19:05, Andi Gutmans wrote:
> > Hey guys,
> >
> > I think the PHP 5 tree has matured a lot and it's time to release an RC. I
> > think end of November or mid-December makes sense. I'd like to aim at the
> > fo
On Tue, 2003-11-11 at 19:05, Andi Gutmans wrote:
> Hey guys,
>
> I think the PHP 5 tree has matured a lot and it's time to release an RC. I
> think end of November or mid-December makes sense. I'd like to aim at the
> former date.
> Are there any major (as in "major") issues which in your
> opi
Hi!
>
> I think the PHP 5 tree has matured a lot and it's time to release an RC. I
> think end of November or mid-December makes sense. I'd like to aim at the
> former date.
thats too fast, or do you mean Nov/Dec. 2004? Why such a hurry? Shouldn't we
have a feature freeze first and try to releas
Why didn't you ask me (or someone else who is keen on tne doc
translation) first while I've repeatedly tried letting you guys know
what to do participate in the activity..? Please drop us a line on an
appropriate mailing list before your enrollment.
Thanks,
Moriyoshi
On 2003/11/12, at 4:14, Sos
To translate PEAR docs into Japanese continuously.
There are lots of docs to translate, and I hope to help it.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hey guys,
I think the PHP 5 tree has matured a lot and it's time to release an RC. I
think end of November or mid-December makes sense. I'd like to aim at the
former date.
Are there any major (as in "major") issues which in your
opinion still need to be dealt with?
Thanks,
Andi
--
PHP Internal
4.3/ext/mbstring/mbstring.c: In function `php_mb_gpc_encoding_converter':
4.3/ext/mbstring/mbstring.c:3729: warning: `ret' might be used uninitialized in this
function
4.3/ext/mbstring/mbstring.c: In function `php_mb_gpc_encoding_detector':
4.3/ext/mbstring/mbstring.c:3792: warning: `encoding' mig
Alexey Trunyov wrote:
Why shouldn't ibase_errcode() function get backported from HEAD to PHP_4
branch? It requires only minor changes, I did that and it works fine for
now.
I agree that it's a minor change, so backporting it would be trivial.
However, the PHP_4 branch is bug fixes only, and in m
35 matches
Mail list logo
