On 04.03.2008 21:28, Stanislav Malyshev wrote:
Hi!
Right.
Please take more time if needed, no need to rush and release something
half-working.
If it takes several months to prepare 5.3 release, let it be so.
With this approach we would never release 5.3 - each couple of months
On Tue, 2008-03-04 at 20:17 +0100, Hannes Magnusson wrote:
I'll hunt you all down and make you eat 1kg of vegetables each day
after the 5.3 release untill proper documentation and upgrade guides
have been written.
I already eat that much vegetables a day..what's my punishment? :-p
(and Pierre
Hi,
Ok so we have a wiki up and running at wiki.php.net. It is integrated
with master.php.net, so you can use your cvs password to login. Pierre
and I are currently the only ones with admin accounts, but aside from
administration of ACL's etc anyone with a CVS based login can create,
Hi.
I don't know if it is a bug or not.
But, having just inherited a load of code which are UTF-8 encoded and
all have a BOM marker, all the BOM markers are being sent to the
browser. This screws up sessions as output is sent before headers
(obviously).
The files are english/non english mix, so
On Wednesday 05 March 2008 11:21:14 Richard Quadling wrote:
But, having just inherited a load of code which are UTF-8 encoded and
all have a BOM marker, all the BOM markers are being sent to the
browser. This screws up sessions as output is sent before headers
(obviously).
The files are
On Tue, 2008-03-04 at 20:38 +0100, Hannes Magnusson wrote:
- .htaccess-like .ini files undocumented
Heh? You mean the .htaccess FastCGI thingy?
user.ini is better. It's not htaccess. :)
And this is what Pierre promised to document along with the thing below.
- [HOST=] and [PATH=] .ini
Quoting Stefan Walk [EMAIL PROTECTED]:
Additionally, i don't think PHP has ignored the BOM before.
Bug #22108 [1] has the gory details. The gist is that this behaves
differently depending on whether PHP was configured with
--enable-zend-multibyte. With the option, the BOM is parsed, used
Philip Olson wrote:
As for where the mentor SoC money goes, I think it finds its way
towards random PHP user groups.
On Tue, Mar 4, 2008 at 11:48 PM, Rasmus Lerdorf [EMAIL PROTECTED] wrote:
The money goes directly to the students. PHP as a project does not take
any money.
Good to know about the Wiki, too, Phillip. I actually saw an
email come in this morning with the wiki.php.net domain as the
subject. Maybe I'd been missing a lot of the discussion somehow, I
didn't know that it was still moving forward.
Lukas has been very quick and responsive on
Hi!
Even though I do agree that delaying the release every 2-3 months is bad,
I believe this particular case deserves some special treatment.
Why? We have perfectly working parser now and no immediate need to
replace it. I agree that new parser is faster and better, but we are
perfectly
Hi!
Ok so we have a wiki up and running at wiki.php.net. It is integrated
Great! Thanks a lot!
Maybe we should import traits proposal there now?
And migrate todo lists too? :)
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL
Hi Stan,
On Wed, Mar 5, 2008 at 6:41 PM, Stanislav Malyshev [EMAIL PROTECTED] wrote:
Hi!
Ok so we have a wiki up and running at wiki.php.net. It is integrated
Great! Thanks a lot!
Maybe we should import traits proposal there now?
And migrate todo lists too? :)
Yes, that's the plan.
On 2007-12-31 14:53, Christian Hoffmann wrote:
There is another problem though: Tests which spawn their own php
interpreter (such as Zend/tests/bug40236.phpt) do not load tmp-php.ini
but use the global ini file which does contain extension* directives.
These tests break.
Ok, meanwhile I went
Dmitry Stogov wrote:
dmitryWed Mar 5 13:34:16 2008 UTC
Modified files: (Branch: PHP_5_3)
/php-src NEWS
/php-src/main fopen_wrappers.c fopen_wrappers.h main.c
/ZendEngine2 zend.c zend.h zend_vm_def.h zend_vm_execute.h
Log:
Hi!
This is a very nice addition - I wonder if you might be interested in a
patch to enable stream wrappers in include_path? There are a couple of
ways this could be done, but the one I think would be best is checking
for // immediately following : and then attempting to locate a
stream
On 05.03.2008, at 18:54, Pierre Joye wrote:
Hi Stan,
On Wed, Mar 5, 2008 at 6:41 PM, Stanislav Malyshev [EMAIL PROTECTED]
wrote:
Hi!
Ok so we have a wiki up and running at wiki.php.net. It is
integrated
Great! Thanks a lot!
I should have also mentioned that in fact Pierre was the
Hi,
I would like to deprecate php_dirname() in 5_3 as it has been moved to
the engine (zend_dirname()). Any concerns?
5_3: http://lars.schokokeks.org/php/5_3-deprecating-php_dirname.diff
HEAD: http://lars.schokokeks.org/php/HEAD-removing-php_dirname.diff
cu, Lars
signature.asc
Description:
Hi,
Am Mittwoch, den 05.03.2008, 18:54 +0100 schrieb Pierre Joye:
[...]
Yes, that's the plan. Lukas will do it as far as I remember. I also
updated the syntax hightlighter (code tag), it sill uses Geshi but in
a nicer way (for those interested, it is the code2 plugin). Nice urls
should also
hi,
On Thu, Mar 6, 2008 at 12:19 AM, Lars Strojny [EMAIL PROTECTED] wrote:
Hi,
I would like to deprecate php_dirname() in 5_3 as it has been moved to
the engine (zend_dirname()). Any concerns?
5_3: http://lars.schokokeks.org/php/5_3-deprecating-php_dirname.diff
HEAD:
Hi Pierre,
Am Donnerstag, den 06.03.2008, 01:22 +0100 schrieb Pierre Joye:
[...]
5_3: http://lars.schokokeks.org/php/5_3-deprecating-php_dirname.diff
HEAD: http://lars.schokokeks.org/php/HEAD-removing-php_dirname.diff
What's the gain of this change besides forcing code change and adding
On Thu, Mar 6, 2008 at 1:26 AM, Lars Strojny [EMAIL PROTECTED] wrote:
Hi Pierre,
Am Donnerstag, den 06.03.2008, 01:22 +0100 schrieb Pierre Joye:
[...]
5_3: http://lars.schokokeks.org/php/5_3-deprecating-php_dirname.diff
HEAD:
Hi Pierre,
Am Donnerstag, den 06.03.2008, 01:30 +0100 schrieb Pierre Joye:
[...]
I'm talking about extension developers. We will all have to add yet
another #ifdef for this function, in the implementation or to define
php_dirname to keep the implementation clean(er). As it is good to
clean up
On Thu, Mar 6, 2008 at 1:32 AM, Lars Strojny [EMAIL PROTECTED] wrote:
Hi Pierre,
Am Donnerstag, den 06.03.2008, 01:30 +0100 schrieb Pierre Joye:
[...]
I'm talking about extension developers. We will all have to add yet
another #ifdef for this function, in the implementation or to
I would like to help maintain the documentation and possibly php.net. I would
also be looking forward to actually develop php runtime and an official bundled
php extension possibly in the near future.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
I'm talking about extension developers. We will all have to add yet
another #ifdef for this function, in the implementation or to define
php_dirname to keep the implementation clean(er). As it is good to
clean up codes, I'm not sure to remove this function is a good thing.
On Mar 5, 2008, at 9:52 PM, David Coallier wrote:
I'm talking about extension developers. We will all have to add yet
another #ifdef for this function, in the implementation or to
define
php_dirname to keep the implementation clean(er). As it is good to
clean up codes, I'm not sure to remove
On 06.03.2008, at 00:45, Lars Strojny wrote:
Hi,
Am Mittwoch, den 05.03.2008, 18:54 +0100 schrieb Pierre Joye:
[...]
Yes, that's the plan. Lukas will do it as far as I remember. I also
updated the syntax hightlighter (code tag), it sill uses Geshi but in
a nicer way (for those interested, it
27 matches
Mail list logo
