On 8/14/07, Stanislav Malyshev [EMAIL PROTECTED] wrote:
A Major bugfix maybe ( yes, it was clearly a bug/misfeature)
A bug is when code doesn't do what was intended. This is not the case,
this is the case of missing feature. While I think everybody agrees this
feature is good to us, it's
Hannes Magnusson wrote:
On 8/14/07, Stanislav Malyshev [EMAIL PROTECTED] wrote:
A Major bugfix maybe ( yes, it was clearly a bug/misfeature)
A bug is when code doesn't do what was intended. This is not the case,
this is the case of missing feature. While I think everybody agrees this
feature
This patch breaks PEAR phar install on 64bit.
From what I can see in the source code, it compares data in the phar with
the result of sprintf(%u..), which is different on 32bit and 64bit because of
this patch.
Either phar should be changed to detect this situation or this patch should be
Hello Larry,
even if their other main language is JS - they still do not have namespaces
or packages and even if both languages have something. I'd rather confuse
people that only know two languages which are very different anyways than
confusing the probably much bigger group of people that
Hello Stanislav,
JS has not much in common with PHP so it shouldn't be used as just another
language to steal ideas from. Actually we are speaking of an OO feature here
and when it comes to that than the two are very different. PHP on the one
hand uses class based OO (like C++ and Java) while
Yeah and we reviewed the patch and saw it was good.
I think what's missing here is that to the best of my knowledge Ilia
reached out off list to revert the patch but when that didn't happen
after 2-3 days it was reverted. So the missing link here is the offlist
email. It was definitely not a screw
Hi Andi
On 8/14/07, Andi Gutmans [EMAIL PROTECTED] wrote:
Yeah and we reviewed the patch and saw it was good.
Thats great, and the author of it would definitely like to hear that
as a reply to his post.
I think what's missing here is that to the best of my knowledge Ilia
reached out off list
I am not the one that want to put more fire in this entire
discussion... I'm tired of listening (this is like package or like
namespace or because my students like it or even that PHP has a unique
implementation).
I've read all comments and I think I can give my 2 cents.
Instead of keep talking
OO. And anyway, are we struggling to find excuses here? Can we in no way
ever at least try to be consistent in anything we do? That JS argument is an
How consistent had acquired a meaning of doing it my way? There's
nothing inconsistent in the name namespace and it is very consistent
with
On 8/14/07, Guilherme Blanco [EMAIL PROTECTED] wrote:
I am not the one that want to put more fire in this entire
discussion... I'm tired of listening (this is like package or like
namespace or because my students like it or even that PHP has a unique
implementation).
I've read all comments
On 8/14/07, Stanislav Malyshev [EMAIL PROTECTED] wrote:
OO. And anyway, are we struggling to find excuses here? Can we in no way
ever at least try to be consistent in anything we do? That JS argument is an
How consistent had acquired a meaning of doing it my way? There's
nothing
On 8/14/07, Antony Dovgal [EMAIL PROTECTED] wrote:
This patch breaks PEAR phar install on 64bit.
From what I can see in the source code, it compares data in the phar with
the result of sprintf(%u..), which is different on 32bit and 64bit because
of this patch.
Either phar should be
On Tuesday 14 August 2007, Guilherme Blanco wrote:
Subject: File Struture
Comments:
Namespace do not restrict directories (AFAIK)
Packages restrict directories (each package have a directory with its
name, like Zend/Cache/File.php)
Question: What is the behavior of PHP in this situation?
13 matches
Mail list logo
