PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (624 total including feature requests)
===[*Compile Issues]==
43389 Open configure ignoring --without-cdb flag
On 16.02.2008, at 02:14, Lars Strojny wrote:
I've heard that E_DEPRECATED is still missing nevertheless its
introduction is planned for 5.3. So I've wrote it [1] based on a
slightly outdated patch by Felipe. The patch is so far complete, as
far
Thx!
as I can tell, but one thing I'm
Hi Lukas,
Am Montag, den 18.02.2008, 10:33 +0100 schrieb Lukas Kahwe Smith:
[... deprecated ini settings ...]
like others have said .. yes .. these should emit deprecated warnings.
Would be great if someone could give me a hint where this should be
done. I'm pretty new to the php-src, so I need
PHP 6 Bug Database summary - http://bugs.php.net
Num Status Summary (57 total including feature requests)
===[*General Issues]==
26771 Suspended register_tick_funtions crash under threaded webservers
On 16.02.2008, at 11:05, Marcus Boerger wrote:
Hello Steph,
so here's my take on the matters. For 5.4 we collect ideas and
implement
them. So that 5.4 comes out with mostly PECL. I guess we can collect
action
items on Lukas' wiki.
Well maybe we should target this stuff for PHP6 for
Hi All,
I'm working for an hosting company, we have a lot of PHP users and see regularly that one of the
scripts from our users is hacked. Result?, a lot of spam on the net, and a lot of work the find the
spamming scripts on the servers.
If you have a PHP script that sends mail, the
Hey,
Paul van Brouwershaven wrote:
I think it should be usefull to add the PHP mail() header patch from
Steve Bennett in safemode by default.
I wonder how this would go along with:
http://www.php.net/~derick/meeting-notes.html#safe-mode
I don't know if this still applies, it's from 2005
Hi Paul,
Am Montag, den 18.02.2008, 12:06 +0100 schrieb Paul van Brouwershaven:
[...]
I think it should be usefull to add the PHP mail() header patch from
Steve Bennett in safemode by default.
As safemode is going to be (finally!) removed in PHP 6, I would propose
not to make this dependent on
2008/2/18, Paul van Brouwershaven [EMAIL PROTECTED]:
Enabling it from the php.ini would also be a good option, the main point is
to get some help with
tracking the spam source in a shared hosted environment.
IIRC Ilia had a better patch for this, I dont know why it hasnt been
merged into PHP
Lukas Kahwe Smith wrote:
Are you aware of the following:
http://ilia.ws/archives/149-mail-logging-for-PHP.html
The idea is the same, but why is this not in the core?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 18.02.2008, at 15:04, Paul van Brouwershaven wrote:
Hi Lars Markus,
Lars Strojny wrote:
As safemode is going to be (finally!) removed in PHP 6, I would
propose
not to make this dependent on safe-mode. I would rather allow this
feature to be enabled separetely in the php.ini. Something
Hi Lars Markus,
Lars Strojny wrote:
As safemode is going to be (finally!) removed in PHP 6, I would propose
not to make this dependent on safe-mode. I would rather allow this
feature to be enabled separetely in the php.ini. Something like
mail.extra_log_header (not the perfect name, I know)
Hi All,
I second this. Can we please re-open the discussion on anonymous
functions as well as closures. That would be an awesome feature.
create_function is a bit ugly semantically to be sufficient for all
anonymous function needs.
Thanks,
Mat
KOYAMA Tetsuji wrote:
Hi lists,
Is this
Hi Chris,
I'd like to see pecl4win merged into pecl.php.net (adding to Steph's
idea of releasing binaries on pecl.php.net), and the Windows binaries
being built from their correct branch (whatever happened to this
project - it seemed so close?)
What happened to this idea is there's no
Steph Fox wrote:
Hi Lukas,
Well maybe we should target this stuff for PHP6 for the time being. A
possible PHP 5.4 would then be a collection of PHP6 todo items that we
want to fast track, or are you guys already certain about PHP 5.4?
I'm thinking 'get the mechanisms into place in 5.4,
On Wed, February 6, 2008 6:39 pm, Stanislav Malyshev wrote:
This topic was already discussed here but never arrived to a
conclusion,
so I will raise it again.
The Problem:
We have $_REQUEST superglobal, which is often used to abstract
GET/POST
requests. However, in most cases we do not want
On Mon, February 18, 2008 1:27 pm, [EMAIL PROTECTED] wrote:
?php
trait ezcReflectionReturnInfo {
function getReturnType() { /*1*/ }
function getReturnDescription() { /*2*/ }
}
class ezcReflectionMethod extends ReflectionMethod {
use ezcReflectionReturnInfo;
So it's just like
On Wed, February 6, 2008 7:20 am, Derick Rethans wrote:
On Wed, 6 Feb 2008, Sam Barrow wrote:
On Wed, 2008-02-06 at 09:31 +0100, Derick Rethans wrote:
I still we should add simple static typehints (ie. just the types
that
we use in the manual) - and they should behave in the same way
Fantastic. Nice RFC, nice explanation, nice design - I love it.
Can I
+1
already? :)
David
Am 18.02.2008 um 20:27 schrieb [EMAIL PROTECTED] [EMAIL PROTECTED]
marr.de:
Hi,
during last six months I've studied a language construct called
Traits.
It is a construct to allow
So it's just like an include for a re-used body of 'class' code.
H.
Why not just allow 'include' here instead?
Well, think this would be a Mixin mechanism like in Ruby.
Forgive me if I'm missing something subtle/complex here, but I wonder
if a Trait is really the right answer...
Yes,
Hi David,
On Feb 19, 2008 12:08 AM, David Coallier [EMAIL PROTECTED] wrote:
Read the proposal, read about traits, read the thesis, read the patch,
then if you still don't understand, give up, and if you do understand,
you can complain.
If you don't understand, ask. If you still don't
Hey everyone,
I have thought about a new feature for some days now. The initial plan
was to create a new keyword deprecated which should simply trigger a
warning when the right error level was set. This could have been
combined with the E_DEPRECATED level from 5.3 (maybe, otherwise
On Monday 18 February 2008, Richard Lynch wrote:
On Mon, February 18, 2008 1:27 pm, [EMAIL PROTECTED] wrote:
?php
trait ezcReflectionReturnInfo {
function getReturnType() { /*1*/ }
function getReturnDescription() { /*2*/ }
}
class ezcReflectionMethod extends
Larry Garfield wrote:
You also note that this mechanism has no runtime impact. That's unfortunate,
because I'd find the ability to add methods to an object at runtime
conditionally based on some other value far more useful in my work. :-)
Especially since, as above, there seems to be a
On Monday 18 February 2008, Rasmus Lerdorf wrote:
Larry Garfield wrote:
You also note that this mechanism has no runtime impact. That's
unfortunate, because I'd find the ability to add methods to an object at
runtime conditionally based on some other value far more useful in my
work. :-)
2008/2/19, Cristian Rodriguez [EMAIL PROTECTED]:
2008/2/19, Felipe Pena [EMAIL PROTECTED]:
Proposed:
- Shows error message (Fatal error, as happens with objects) for
integer and float variables.
http://felipe.ath.cx/diff/bug39915.diff
+1 , fatal error for consistency.
you need
[EMAIL PROTECTED] schrieb:
The following RFC deals with the questions what Traits are, how they are
used, why they are usefull and how they do look like in PHP.
Thank you, Stefan, for your thorough RFC.
A patch implementing this new language construct is available, too.
I tested an
Rasmus Lerdorf schrieb:
The idea here is that we want to be able to cache opcodes, classes and
functions and optimize them out of the runtime context so the executor
can skip creating classes and functions on every single request.
Thanks to their Flattening Property, there should be no notion
Rasmus Lerdorf schrieb:
This was in response to the suggestion that it should be extended to do
runtime conditional modification of the classes.
Ah, sorry.
--
Sebastian Bergmann http://sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867
29 matches
Mail list logo
