With ze_fetch_arguments I meant zend_parse_parameters (just a small
spelling error.. ;-) )
--
// DvDmanDT
mail: dvdmandt¤telia.com
msn: dvdmandt¤hotmail.com
""Corne"" <[EMAIL PROTECTED]> skrev i meddelandet
news:[EMAIL PROTECTED]
> Hi,
>
> I was trying to make PHP a bit more type-safe, but until
First of all, this doesn't seem like a very good idea to do.. My suggestions
below are for the first idea (throw a warning/error if a variable changes
type).
Second, I have never hacked the engine, and don't really have any ideas on
how it accutually works, I'm just guessing here.
Next, my fir
Hello Brian,
I am not yet convinced we need to do anything. If one wants to execute non
default test environment then one can simply use the environment variables
and be done. It sounds pretty much as that is a problem of people writing
deployment scripts. Actualyl the problem seems to be findin
This patch should safely remove what appears to be unnecessary strlen
() calls for php_valid_var_name() used by extract().
diff --git a/ext/standard/array.c b/ext/standard/array.c
index fad4bf2..401957f 100644
--- a/ext/standard/array.c
+++ b/ext/standard/array.c
@@ -1270,15 +1270,13 @@ PHP_FU
On Tue, December 5, 2006 4:45 pm, Arnold Daniels wrote:
> Richard Lynch schreef:
>> On Mon, December 4, 2006 7:21 pm, Arnold Daniels wrote:
>>
>>> I'm struggling with the problem that cross-referenced objects don't
>>> get
>>> destroyed. I can off course write a method to break the
>>> cross-refere
Rather than re-designing the language, you might want to begin using:
http://php.net/assert
in your code...
Just giving you an option you may have missed -- Not claiming you're
"wrong"
On Tue, December 5, 2006 2:45 pm, Corne wrote:
> Hi,
>
> I was trying to make PHP a bit more type-safe, but unti
I wish I could write bug reports this good!
:-)
Nice work!
On Tue, December 5, 2006 11:22 pm, Kevin Hoffman wrote:
> Bug summary
>
> If putenv deletes an environment variable (putenv("VAR=")) after it
> was set previously (putenv("VAR=xxx")) then pe->previous_entry (pe i
Hello Marcus,
On Dec 4, 2006, at 11:37 AM, Marcus Boerger wrote:
Hello Luca,
we cannot do that. This patchwould prevent loading of any shared
extension. And we decided against using dl() in the test scripts
some years
ago. The only thing we can do here is having a new make thing that
do
On Thu, December 7, 2006 9:17 am, Zeev Suraski wrote:
> At 13:35 07/12/2006, Stefan Esser wrote:
>>Guys,
>>
>>why can't you simply introduce a new variable type for serialized
>>strings like uppercase S:
>>There is absolutely no need for breaking backward compatibility.
>
> I can't think of a singl
Just a quick notice to everyone that I'll be making RC1 of 5.2.1 on
Thursday (Nov. 14th) after which only bug fixes will be allowed into
the tree. So, if you have any major commits pending, now the time to
make them. This will be the only RC this year and will be followed by
RC2 in the 1st
Hello,
On 12/9/06, Hannes Magnusson <[EMAIL PROTECTED]> wrote:
On 12/9/06, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
> Ok, I think COM has been sufficiently well defended for now, so it
> stays hopefully someone(s) will find the time to look at the bugs and
> close and bogus them as needed.
>
On 12/9/06, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
Ok, I think COM has been sufficiently well defended for now, so it
stays hopefully someone(s) will find the time to look at the bugs and
close and bogus them as needed.
As far mhash & socket, I agree that it would be wrong to remove them
in
Ok, I think COM has been sufficiently well defended for now, so it
stays hopefully someone(s) will find the time to look at the bugs and
close and bogus them as needed.
As far mhash & socket, I agree that it would be wrong to remove them
in 5.2, so let's remove them for now in PHP 6.0 and w
Hello Ilia,
-1 (*), +1, +1, but I think you mean 5.3 as we have released 5.2 already
and I think it is a bad idea to drop in bugfix releases.
(*) If someone takes over i am fine with keeping it. I don't like stuff
nobody takes care of. If we cannot maintain it, it mostlikely has issues.
And tho
Ilia Alshanetsky wrote:
> COM:
-0
> mhash:
+1
> sockets:
+1 for PHP6
Regards,
--
Michael
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Ilia Alshanetsky wrote:
COM:
-1. Its core for windows, has little impact on non-windows users other
than a few extra KB to download, and works for the most part.
mhash:
sockets:
+1 for both
Rob
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net
On 12/8/06, Andi Gutmans <[EMAIL PROTECTED]> wrote:
As far as finding a maintainer is concerned, we can check again with Wez. If
he doesn't have time we should probably be able to find someone who can look
into some of those bugs. Despite bugs, I've never had issues with it.
I'm currently (way!
On 12/8/06, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
COM:
Un-maintained at this time and has a fairly serious number of bugs
(26 by latest count, many of which are crashes)
But aside from those problems (which I suspect are mostly duplicates),
it works fine for the majority of users.
Hannes,
please do not try to get yourself involved in things you do not understand.
> The report your are thinking about was bogus - and had nothing to do
> with Suhosin.
-Stefan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 12/8/06, Stefan Esser <[EMAIL PROTECTED]> wrote:
>> >> c) Support Cookies correctly...
>> Very simple: In some earlier version php_register_variable_ex was
>> changed to handle cookies different from other variables: Cookies with
>> the same name will get dropped after the first is registered
20 matches
Mail list logo
