On 06.11.2008, at 06:17, Mark wrote:
Hi,
We got some problems with PHP with wddx functions which consider PHP's
side will always be "ISO-8859-1".
I wrote/tested a patch to fix this issue, against PHP 5.2.7rc2.
Bugreport:
http://bugs.php.net/bug.php?id=46496
NB: the bug has been marked "bo
On Thu, 2008-11-06 at 22:19 -0600, Josh Thompson wrote:
> I don't understand why in the namespaced example no one seems to have a
> problem with new A() meaning new \foo\bar\A(), but we can't use the *
> wildcard to do the same thing?
Since we don't reliable know all possible classes, think abou
On Nov 6, 2008, at 6:27 PM, Nate Abele wrote:
I was shocked and horrified that that ridiculous "remove-the-$"
post actually turned into a legitimate discussion. I mean, seriously?
No, not seriously.
It's an old internet joke, a shibboleth among programmers, not unlike
"GOTO considered h
Stan Vassilev | FM wrote:
use foo\bar\*;
$a = new A();
$b = new B();
...
I may be asking this question out of ignorance, but here goes:
What is the difference between the following snippets?
// global.php
use \foo\bar\*;
$a = new A();
$b = new B();
// namespaced.php
namespace \foo\bar;
$a
On 06.11.2008, at 18:46, Stan Vassilev | FM wrote:
> NOTE: Continuing from thread "Call it: allow reserved words in a
> class or not?":
[snip]
>
> We can test such automated porting scripts on samples collected from
> PEAR, Google Code and projects like Drupal, Joomla etc. to reduce
> side effec
The third & final release candidate of 5.2.7 was just released for
testing and can be downloaded here:
http://downloads.php.net/ilia/php-5.2.7RC3.tar.bz2 (md5sum:
0e336c04c49c8614cab0c4c4a9c3b681)
The Windows are available as well at the following URL: http://windows.php.net/qa/
. The numb
Hi!
a) I showed the 5.2 behavior, using "proper" interfaces is a silent
change which might break application and is probably hard to find. While
I don't know how many people rely on these "features".
I think it'd be OK for functions using HASH_OF in 5.2 keep using that,
and I'm not sure we sh
On Thu, 2008-11-06 at 23:21 +0200, Stan Vassilev | FM wrote:
> The exception should be made for any class implementing the relevant SPL
> interfaces, and that's not just ArrayObject.
>
> It may be seen as just "one class" but actually all of the "transparent"
> iterator implementations (for iter
Hi,
I'd completely agree with that patch - it's very useful for me since I only
build applications based on arrays;
I'll try to apply some other modifications - and maybe we got it ;-D
- benchmarking the app core-
Your,
--
(c) Kenan Sulayman
Freelance Designer and Programmer
Life's Live Poetry
On Thu, Nov 6, 2008 at 22:06, Johannes Schlüter <[EMAIL PROTECTED]> wrote:
> On Thu, 2008-11-06 at 10:10 -0800, Stanislav Malyshev wrote:
>> Hi!
>>
>> > So as suggested and wished, here is a patch that add a modifier '%' to
>> > 'a' in parameter parsing API, where it allows object that implements
>
So allowing passing objects to array stuff using HASH_OF can lead to
unexpected behavior. Dropping the old behavior makes this clear ... but
is bad for stuff like ArrayObject.
I'm not sure whether we should add special rules for a single class
though ..
johannes
The exception should be made fo
On Thu, 2008-11-06 at 10:10 -0800, Stanislav Malyshev wrote:
> Hi!
>
> > So as suggested and wished, here is a patch that add a modifier '%' to
> > 'a' in parameter parsing API, where it allows object that implements
> > ArrayAccess to be accept. Although it doesn't invoke any their methods,
> > i
Hi,
This are tentatively looking like alpha3 could hit on November 18th.
So everybody please try to get whatever you are working on ready to be
finished and committed by no later than 13th. So that packaging can
happen on a stable tree on the 17th.
regards,
Lukas Kahwe Smith
[EMAIL PROTECTE
On Nov 5, 2008, at 7:22 AM, Graham Kelly wrote:
Hi,
I played with a patched version of compare_function with this
optimization in it. Other then for strings it didn't seem to make
much of a difference. A quick test showed that in an average php
application only about 0.15% of calls to co
Hi!
As you know, with the new convention, the parser will not encounter
T_STRING "Zend\Validate\Interface" but rather:
With namespaces, class name would not be Zend\Validate\Interface. Having
namespaces, it would make much more sense to make last component a
descriptive name, so you won't ha
Em Qui, 2008-11-06 às 10:10 -0800, Stanislav Malyshev escreveu:
> Hi!
>
> > So as suggested and wished, here is a patch that add a modifier '%' to
> > 'a' in parameter parsing API, where it allows object that implements
> > ArrayAccess to be accept. Although it doesn't invoke any their methods,
>
Hi!
As you know, with the new convention, the parser will not encounter T_STRING
"Zend\Validate\Interface" but rather:
With namespaces, class name would not be Zend\Validate\Interface. Having
namespaces, it would make much more sense to make last component a
descriptive name, so you won't h
Hi!
So as suggested and wished, here is a patch that add a modifier '%' to
'a' in parameter parsing API, where it allows object that implements
ArrayAccess to be accept. Although it doesn't invoke any their methods,
i.e. just how it works nowdays.
I think if you use HASH_OF then any object hav
> PHP may be a hybrid language, but the fact is you're implementing object
> oriented functionality, and as such should be implementing it in a way that
> follows de-facto standards in object oriented language design. I should be
> able to overload your internal array object, and yes, arraysshould
On 06.11.2008, at 18:46, Stan Vassilev | FM wrote:
NOTE: Continuing from thread "Call it: allow reserved words in a
class or not?":
As much as I'd love to see more case-sensitivity, I'm afraid it would
break quite a lot of existing apps, according to Google Code.
http://www.google.com/code
NOTE: Continuing from thread "Call it: allow reserved words in a class or not?":
> As much as I'd love to see more case-sensitivity, I'm afraid it would
> break quite a lot of existing apps, according to Google Code.
>
> http://www.google.com/codesearch?q=lang%3Aphp+%3D%5Cs%2AArray
>
> -JD
It's
2008/11/6 Stan Vassilev | FM <[EMAIL PROTECTED]>:
>
> There's one trivial solution: make the keywords and class names
> case-sensitive. Then classes "If", "Array", "Interface" will never class
> with the all-lowercase keywords.
As much as I'd love to see more case-sensitivity, I'm afraid it would
Hi,
Watching my thread devolve into a blamefest wasn't the intention. I just
wanted a clear answer if something's done about it or not.
To everyone participating in the thread: guys it's NOT trivial in the
current situation. To the parser, a separate string matching a keyword is
the token k
So as suggested and wished, here is a patch that add a modifier '%' to
'a' in parameter parsing API, where it allows object that implements
ArrayAccess to be accept. Although it doesn't invoke any their
methods,
i.e. just how it works nowdays.
I applied this to HEAD and ran a few minor (manua
I applied this to HEAD
Oops. I mean to PHP_5_3 (keep forgetting that it's not HEAD).
S
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Dan wrote:
> Quite.
>
> It does appear as though, as a group, that you're struggling with the entire
> concept of namespaces. As demonstrated by this discussion, the resolution
> issues, the separator farce, and so on.
>
> It may be due to weaknesses in the PHP engine as a whole, I don't know...
Steph Fox a écrit :
Great, so drop PHP and go use Javascript. Oh wait - you can't. Because
*it wasn't designed do the same job*.
For your culture, the first use of javascript (livescript actually),
was to provide server side scripting.
--
Mickaël Wolff aka Lupus Michaelis
http://lupusmic.
On Wed, Oct 22, 2008 at 1:28 PM, John Mertic <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 22, 2008 at 1:16 PM, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
>> You cannot use smart_str_appendc() in this case, since the EOL could be a 2
>> byte string "\r\n".
>>
>> smart_str_appendl(&csvline, PHP_EOL, siz
On Thu, Nov 6, 2008 at 12:15 PM, Dan <[EMAIL PROTECTED]> wrote:
> Okay, I'm not going to sit and argue it... but to anyone looking at these
> issues from outside the PHP internals world (like I am), that argument is
> worthy of ridicule.
What argument? Due to top-posting you're kind of killing the
Dan,
PHP may be a hybrid language, but the fact is you're implementing object
oriented functionality, and as such should be implementing it in a way
that
follows de-facto standards in object oriented language design. I should be
able to overload your internal array object, and yes, arraysshoul
Okay, I'm not going to sit and argue it... but to anyone looking at these
issues from outside the PHP internals world (like I am), that argument is
worthy of ridicule.
PHP may be a hybrid language, but the fact is you're implementing object
oriented functionality, and as such should be implementing
Hi all,
Em Qua, 2008-11-05 às 16:20 +, Geoffrey Sneddon escreveu:
> On 4 Nov 2008, at 22:59, Stanislav Malyshev wrote:
>
> >> so where do we stand here?
> >
> > I'd prefer to have it fixed, but then it probably requires changing
> > the parameters API for 'a', which might lead to some unexp
Ben Davies | Lead Developer | Stickyeyes
-Original Message-
From: Steph Fox [mailto:[EMAIL PROTECTED]
Sent: 06 November 2008 11:59
To: Ben Davies; 'Dan'; 'troels knak-nielsen'
Cc: 'Larry Garfield'; internals@lists.php.net
Subject: Re: [PHP-DEV] Call it: allow reserved words in a class
In .NET, I can stick an Array class into my own namespace, extending the
System.Array type if I want to and use it in my code without issue. Why
can
I not do that here? Is it simply that you're so worried about backwards
compatibility that you feel that you can't make the necessary changes to
t
This namespaces issues highlights the very fundamental issues with PHP, and
glib, childish responses like yours only serve to score points.
===
The 'very fundamental issue' here is that you're expecting namespaces to
allow things that are not legal in non-namespaced PHP code. The entire
thrust
Quite.
It does appear as though, as a group, that you're struggling with the entire
concept of namespaces. As demonstrated by this discussion, the resolution
issues, the separator farce, and so on.
It may be due to weaknesses in the PHP engine as a whole, I don't know...
but it strikes me that mo
> Isn't the ability to do that one of the biggest reasons for having
> namespaces? To avoid having to fill your class names with junk.
> The examples are namespaced appropriately, they tell the developer that
> it's
> a Helper for Arrays in the MyFramework framework. I shouldn't need to
> suffix
On Thu, Nov 6, 2008 at 2:00 PM, Steph Fox <[EMAIL PROTECTED]> wrote:
> This thread really should be re-titled to "allow reserved words as a
> classname or not". Then perhaps the only logical response to the question
> would be so obvious that there would be no thread... oo-er...
+1
my favourite
Isn't the ability to do that one of the biggest reasons for having
namespaces? To avoid having to fill your class names with junk.
The examples are namespaced appropriately, they tell the developer that
it's
a Helper for Arrays in the MyFramework framework. I shouldn't need to
suffix
the class n
Hi Dan,
Am 06.11.2008 um 11:03 schrieb Dan:
Isn't the ability to do that one of the biggest reasons for having
namespaces? To avoid having to fill your class names with junk.
The examples are namespaced appropriately, they tell the developer
that it's
a Helper for Arrays in the MyFramework fr
Isn't the ability to do that one of the biggest reasons for having
namespaces? To avoid having to fill your class names with junk.
The examples are namespaced appropriately, they tell the developer that it's
a Helper for Arrays in the MyFramework framework. I shouldn't need to suffix
the class name
On Thu, Nov 6, 2008 at 10:35 AM, Dan <[EMAIL PROTECTED]> wrote:
> What if you want to provide a set of helper/wrapper classes, appropriately
> namespaced, something along the lines of:
> MyFramework\Helpers\Array
> MyFramework\Helpers\Database
> MyFramework\Helpers\Session
> etc.
>
> If I want to u
What if you want to provide a set of helper/wrapper classes, appropriately
namespaced, something along the lines of:
MyFramework\Helpers\Array
MyFramework\Helpers\Database
MyFramework\Helpers\Session
etc.
If I want to use that naming convention, I don't want to have to name some
of my classes diff
43 matches
Mail list logo
