Rasmus Lerdorf wrote:
Well, that is the point, it didn't actually work. Code similar to this
caused memory corruption. So while you may not have seen an instant
crash, over time and in certain conditions you would get unexplained
crashes. In order to fix this bug we needed to check for this
On Thursday 15 September 2005 06:12, Rasmus Lerdorf wrote:
Makoto Tozawa wrote:
Jani Taskinen wrote:
Show me one such person please. One that does this using PHP. :)
One that really NEEDS this to be possible..
It's impossible to find one as PHP doesn't support it today.
At 10:23 15/09/2005, Leigh Makewell wrote:
Rasmus Lerdorf wrote:
Well, that is the point, it didn't actually work. Code similar to this
caused memory corruption. So while you may not have seen an instant
crash, over time and in certain conditions you would get unexplained
crashes. In order
Hi,
For performance' sake, I have to know if this is true:
Is it the case that when I do this:
?php
$array = array(one = array(0,1,2), two = array(4,5,6));
$one = $array[one];
?
That $one is not a copy, but a reference to $array[one] and will only
become a copy when I alter the contents of
At 13:35 15/09/2005, Ron Korving wrote:
Hi,
For performance' sake, I have to know if this is true:
Is it the case that when I do this:
?php
$array = array(one = array(0,1,2), two = array(4,5,6));
$one = $array[one];
?
That $one is not a copy, but a reference to $array[one] and will only
Yes it is legal because it worked
That's nonsense. Even in the C-language certain things have worked in the
past because of compiler bugs. Newer GCC versions have fixed it and broken
C-code. Too bad for the users, but it improved the compiler's C-compliance.
Something might work, but that
On Thu, 15 Sep 2005, Leigh Makewell wrote:
joke. People critisise and joke about PHP's automatic Bogus bot that just
trolls through the database and marks any submitted bugs as Bogus. What is
the point of making the bug database public?
1) I'm not a bot.
2) I'm not bogusing
Perfect :)
I've been doing it wrong all the time, thinking I was improving performance.
It's good to know how things really work under the hood.
Thanks,
Ron
Zeev Suraski [EMAIL PROTECTED] schreef in bericht
news:[EMAIL PROTECTED]
At 13:35 15/09/2005, Ron Korving wrote:
Hi,
For
I don't care about this as long as I can DISABLE it from
my PHP builds (and not be forced to link it with ICU).
--Jani
On Wed, 14 Sep 2005, Rasmus Lerdorf wrote:
Makoto Tozawa wrote:
Jani Taskinen wrote:
Show me one such person please. One that does this using PHP. :)
Zeev Suraski wrote:
Let me let you in on a secret as well. This tone isn't going to get you
anywhere.
No it won't. But the diplomatic one didn't get us anything except
insults and put downs. This approach has at least got some serious
attention. :)
For the record, I was against fixing
Rasmus Lerdorf wrote:
That's fine, and you shouldn't care, I agree. I argued much the same
point just yesterday in a chat with Ilia. You do however seem to be
glossing over the fact that this new check can be very helpful. Take
this case:
sort(array(3,2,1));
Or any other example where the
On 9/15/05, Leigh Makewell [EMAIL PROTECTED] wrote:
[...] There are too many viable
options out there to warrant sticking with the relatively fragile and
limited PHP platform. Change to Ruby. It's heaps better!
FWIW, Ruby is changing as well.
Regards,
Michael
--
PHP Internals - PHP Runtime
I think he has a point. Regardless, I'd like to add something else:
Right now, BC has been broken and non-transparent, illogical behaviour been
introduced due to engine internals. It will never be obvious nor logical to
new users why they cannot return a new Object() or whatever without using a
Marcus Boerger wrote:
Hello Edin,
well imho it makes no sense to prefix all the iterators with Spl and also
most of them are released already with 5.0. Changing those is to big of a BC
issue isn't it? I mean it is different from changing a few consts very
rarely used to class consts.
Edin Kadribasic schrieb:
Now, you claim they cannot be renamed due to the BC concerns
I think we should break BC for PHP 5.1 and prefix the existing classes
with SPL. This is better than the current state in HEAD and PHP_5_1
which is inconsistent.
Hopefully we will have namespaces in PHP
On 9/15/05, Leigh Makewell [EMAIL PROTECTED] wrote:
I believe all of this could of been avoided with careful PR. Now you
need some major PR to repair the damage.
All the points I tried to explain in the last 2 months or so were
about that and only that. Every oppinions have been raised.
If
Well then I suggest you get out there and find out what you are doing
wrong because there is an increasing number of people out there who are
not happy with how their bugs are being treated.
This is a good place to start.
http://www.sitepoint.com/forums/showthread.php?t=297291
Ask them what
On Thu, 15 Sep 2005, Leigh Makewell wrote:
Well then I suggest you get out there and find out what you are doing wrong
because there is an increasing number of people out there who are not happy
with how their bugs are being treated.
This is a good place to start.
Hello Andi, hello Zeev,
MFH and change towards class constants is done. The only part being new
inside SPL now is the ability of spl's autoload to work with non static
loader methods. Do you think i should move that into 5.1 as well?
regards
marcus
Wednesday, September 14, 2005, 9:55:32 PM,
Hello Sebastian,
honestly why do you want to prefix iterators? and secondly i'd be just
plain stupid to prefix the exception classes. In the end we should move
the exception classes into the engine anyways. But who cares what i say
marcus
Thursday, September 15, 2005, 2:08:53 PM, you
On 9/15/05, Leigh Makewell [EMAIL PROTECTED] wrote:
If you don't know why it's wrong to tell them they are stupid,
You are doning something stupid does not mean that you are stupid.
For example, arguing like you do about Jani, is stupid, but you are
certainly not stupid. Notice the difference?
Leigh, that's kinda the point (and to some degree the problem).
This is not a job.
If you don't know why it's wrong to tell them they are stupid, and can't
be bother spending an extra 10 seconds formulating a respectable
response instead, then you are the wrong person for the job.
--
Marcus Boerger schrieb:
honestly why do you want to prefix iterators? and secondly i'd be
just plain stupid to prefix the exception classes.
Bugger, I forgot that those two (iterators and exceptions) are part of
SPL for a second. They're so essential, IMHO, that I thought them part
of the
On Thu, 15 Sep 2005, Leigh Makewell wrote:
If you don't know why it's wrong to tell them they are stupid, and can't be
Show me the report where I have called someone stupid. Then I can explain
you why I did so. :)
bother spending an extra 10 seconds formulating a respectable
Sebastian Bergmann schrieb:
Bugger, I forgot that those two
Just to clarify for those who do not know that Bugger can be used a
phrase along the lines of Oh my God!: I did not call Marcus a bugger,
which would be, given certain meanings of the word as a noun, really bad
name calling.
--
No one is forcing you to upgrade to PHP 6.
--Wez.
On 9/15/05, Jani Taskinen [EMAIL PROTECTED] wrote:
I don't care about this as long as I can DISABLE it from
my PHP builds (and not be forced to link it with ICU).
--Jani
On Wed, 14 Sep 2005, Rasmus Lerdorf wrote:
Hi,
as nobody was able to answer my question on IRC,
I just drop it here:
Is it useless (yet even counter-productive) to enable
pass_by_ref in an ARG_INFO section for a function or
method that expects an object?
By counter-productive I mean that I'd need to actually
pass an identifier for a
Jani Taskinen schrieb:
10 seconds? Sheesh. If english was my native language, maybe I could do
it
that fast but as it isn't, and as I have to first think the phrase in
finnish
then traslate it in my head into english and then write it and then fix
the typos,
it takes
The Oh my God! meaning comes from the fuller phrase Bugger me!;
neither usage is appropriate for polite company.
--Wez.
On 9/15/05, Sebastian Bergmann [EMAIL PROTECTED] wrote:
Sebastian Bergmann schrieb:
Bugger, I forgot that those two
Just to clarify for those who do not know that Bugger
Only use references when you need to be able to overwrite the variable.
--Wez.
On 9/15/05, Michael Wallner [EMAIL PROTECTED] wrote:
Hi,
as nobody was able to answer my question on IRC,
I just drop it here:
Is it useless (yet even counter-productive) to enable
pass_by_ref in an ARG_INFO
Yeah, it's awesome. I heard there's even a number of kids in Finland who can
speak, read and write Finnish. Awesome! ;)
Ron
Oliver Grätz [EMAIL PROTECTED] schreef in bericht
news:[EMAIL PROTECTED]
Jani Taskinen schrieb:
10 seconds? Sheesh. If english was my native language, maybe I
Hi Wez Furlong, you wrote:
Only use references when you need to be able to overwrite the variable.
Ok, and what about return_by_ref?
Thanks,
--
Michael - mike(@)php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Touché. :)
But I must insist. I want to upgrade at some point.
I might even have use for unicode, at some point. But why can't
I disable it as long as it does not give me anything I need?
On other topic, I want to do the spring cleaning we discussed earlier
already in
Hi All,
I could not see the latest snaps of php-5.0.6-dev on
http://snaps.php.net.
But still could I could get
http://snaps.php.net/php5-STABLE-latest.tar.bz2.
With regards
Kamesh Jayachandran
--
http://www.fastmail.fm - A fast, anti-spam email service.
--
PHP Internals - PHP Runtime
At 14:57 15/09/2005, David Zülke wrote:
I think he has a point. Regardless, I'd like to add something else:
Right now, BC has been broken and non-transparent, illogical behaviour been
introduced due to engine internals. It will never be obvious nor logical to
new users why they cannot return a
PHP_5_0 branch is dead meat. Just use PHP_5_1.
--Jani
On Thu, 15 Sep 2005, Kamesh Jayachandran wrote:
Hi All,
I could not see the latest snaps of php-5.0.6-dev on
http://snaps.php.net.
But still could I could get
http://snaps.php.net/php5-STABLE-latest.tar.bz2.
With regards
Kamesh
On 15.09.2005 03:24, Antony Dovgal wrote:
On 14.09.2005 15:20, Zeev Suraski wrote:
Any last minute additions to 5.1.0RC2 or can we roll it?
If it's not too late I'd like to fix http://bugs.php.net/bug.php?id=34505
before RC2.
It'll require addition of zend_unmangle_property_name_ex() and
On 14.09.2005 15:20, Zeev Suraski wrote:
Any last minute additions to 5.1.0RC2 or can we roll it?
It seems that #27145 has crept back into 5.1 with a copy/paste typo.
Here is the patch for it too.
--
Wbr,
Antony Dovgal
Index: Zend/zend_compile.c
Jani,
5_0 is not dead meat right now anymore than 4_4 is. It's going to be used
for quite a while still.
If you had something to do with the removal of the snaps, please revert.
Thanks,
Zeev
At 18:04 15/09/2005, Jani Taskinen wrote:
PHP_5_0 branch is dead meat. Just use PHP_5_1.
On Thu, 15 Sep 2005 22:34:21 +1000, in php.internals [EMAIL PROTECTED]
(Leigh Makewell) wrote:
The people who submit bugs are helping you make the product better. You
should never insult a person for trying to help you. Tell them you are
unable to reproduce the error and then point them to the
Wez Furlong schrieb:
The Oh my God! meaning comes from the fuller phrase Bugger me!;
neither usage is appropriate for polite company.
Rest assured that I will never use that phrase again. Thanks for your
clarification!
--
Sebastian Bergmann
Thanks Zeev and Jani for the clarification.
As long as http://snaps.php.net/php5-STABLE-latest.tar.bz2 is available,
I have no issues about what is shown in the web.
With regards
Kamesh Jayachandran
On Thu, 15 Sep 2005 18:17:33 +0300, Zeev Suraski [EMAIL PROTECTED] said:
Jani,
5_0 is not dead
On Thu, 15 Sep 2005, Peter Brodersen wrote:
Comparing php bug reporting to mozilla and mysql (the latter being a
bit unfair comparison with professional workers) I think that mozilla
bogus bugs have better references (to dupes, etc.) and mysql bogus
bugs are even more polite in their template
How does the first part relate to the second part in any way? The
confusion level? If that's your point, then we're doing our best to
decrease confusion rather than foster it. PHP 5 was a big step in the way
with its new object model and the much reduced need for references. As a
matter
Greetings,
My team has added read support for TGA, PIC and SGI formatted images to
the GD library bundled with PHP 5.0.5 can we get this added into the gd
released with php? or anything similar we want to release this code back
to the community.
Debug
--
PHP Internals - PHP Runtime
Nobody _removed_ any snaps. They're just hidden.
And as for PHP_5_0 branch: You may do whatever you want with
it but I don't want to have anything to do with it.
Most of the bugs said fixed are only fixed in PHP_5_1.
There are just too many things broken in PHP_5_0 branch.
Mike Bretz [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Also an useful feature would be const on function parameters.
Hmm, I like that ;) That may even provide a performance increasing
opportunity...
I have another idea I came up with today: regular expression switches, but
it
It does indeed relate. You now have the problem that you have to explain to
people why they cannot do return new FooBar(); in their methods.
Doesn't that only apply to code you write that must be compatible with PHP4?
In which case, is it still something you would have to explain to someone
-Original Message-
From: Jani Taskinen [mailto:[EMAIL PROTECTED]
Was:
Subject: Re: [PHP-DEV] PHP6, Unicode for language functions,
classes,methods, vars names
Touché. :)
But I must insist. I want to upgrade at some point.
I might even have use for unicode, at
At 22:08 15/09/2005, Douglas wrote:
It does indeed relate. You now have the problem that you have to explain to
people why they cannot do return new FooBar(); in their methods.
Doesn't that only apply to code you write that must be compatible with PHP4?
In which case, is it still something
Can be done already ... sorta.
switch (true) {
case ($str == 'abc'):
echo it was ABC!\n;
break;
case (preg_match('/^[0-9]+$/i', $str)):
echo it was a number!\n;
break;
default:
echo it was no
Ron Korving wrote:
I have another idea I came up with today: regular expression switches, but
it would be difficult without adding to the syntax.
no, its actually pretty easy from a syntax point of view,
you don't need to add another keyword, just add an optional
callback parameter to switch()
The following code segfaults after either I call die/exit or call
socketi_accept once again.
Can anyone spot anything working with it?
#ifdef HAVE_CONFIG_H
#include config.h
#endif
#include php.h
#include php_hello.h
#include string.h
#include sys/types.h
#include sys/socket.h
#include netdb.h
Pierre Joye wrote:
On 9/14/05, Greg Beaver [EMAIL PROTECTED] wrote:
http://pear.php.net/go-pear.phar
For the distros, let use the same system. If one would like to
customize, he is free to use go.pear.phar at a later point.
Regards,
--PIerre
go-phear.phear :)
intall-phear :)
Andrey
Derick Rethans wrote:
On Thu, 15 Sep 2005, Peter Brodersen wrote:
I guess my only real suggestion is that some of the template-answers
could be better worded.
Feel free to send a patch, and that was not meant as an attack.
I wrote this sometime back; it may be out of date.
Chris
new_sock-bsd_socket = accept(php_sock-bsd_socket, sa, salen);
In all liklihood it's that.
Now In the nicest way possible, why don't I suggest that you CLEAN UP
YOUR CODE NEXT TIME!?!?! You might have noticed that new_sock isn't alloc'd
if it wern't for all the comments and flat-out bad
Jani,
I don't really see how PHP 6 can support a build
without ICU. With the whole core using the ICU
library it's almost like not supporting libC. If
you find a way I'd be happy to hear about it and
discuss but I think it's not realistic.
Regarding spring cleaning, I suggest to relax a
On 9/16/05, Andi Gutmans [EMAIL PROTECTED] wrote:
Jani,
I don't really see how PHP 6 can support a build
without ICU. With the whole core using the ICU
library it's almost like not supporting libC. If
you find a way I'd be happy to hear about it and
discuss but I think it's not realistic.
On 9/16/05, Andi Debug Ireland [EMAIL PROTECTED] wrote:
I'm not using CVS version of the PHP source what is the CVS information so
i can checkout and merge my code into it and make a patch.
Sorry, I was not clear.
Send me the patch, tell me against wich version it matches. I have to
commit
On 9/16/05, Andi Gutmans [EMAIL PROTECTED] wrote:
I think most of that list can be implemented but while it's easy to
give a +1 and make the changes, I still want to dive into some of
them more. I've been much busier looking at the Unicode stuff and
5.1.x patches so I didn't have a lot of time
On 9/16/05, Andi Gutmans [EMAIL PROTECTED] wrote:
Jani,
I don't really see how PHP 6 can support a build
without ICU. With the whole core using the ICU
library it's almost like not supporting libC. If
you find a way I'd be happy to hear about it and
discuss but I think it's not realistic.
Hello again,
Wow, this thread generated more heat than I thought it would, I
basically just wanted to know the reasoning behind making the change to
PHP4, unfortunate I guess for all involved that it went downhill. I
have learned much in the past few days, at any rate.
As mentioned, my
That's not where it segfaults. The function works perfectly once. If I
attempt to exit /
die or call that function again, it segfaults.
However, I have noticed that if I do not use ZEND_REGISTER_RESOURCE the
program no longer segfaults.
And sorry for the comments, someone people don't write the
That's not where it segfaults. The function works perfectly once. If I
attempt to exit /
die or call that function again, it segfaults.
However, I have noticed that if I do not use ZEND_REGISTER_RESOURCE the
program no longer segfaults.
I didn't say that's where it segfaults, I said that's where
Aha! That was the inspiration I needed to get the right
combination of s. The following bit of code behaves
differently under 4.3 vs 4.4:
?php
function f($a) { return $a; }
$x = array('a','b','c');
foreach (array_keys($x) as $k) {
// I think the following line disconnects $y in 4.3
// but
I should have said something about a fix. I guess the fix
would be to always unset any variable that is attempting
to be assigned by reference before doing anything else
with the variable. Yes? That would at least fix BC
for the example I gave (and I think Colin's example).
If $y were unset
On Sep 15, 2005, at 9:21 AM, Leigh Makewell wrote:
If you don't know why it's wrong to tell them they are stupid, and
can't be bother spending an extra 10 seconds formulating a
respectable response instead, then you are the wrong person for the
job.
A cursory survey of the bugs db
67 matches
Mail list logo
