In general I'd prefer one namespace per-file, at least as a best
practice and common advertised use. For this case it doesn't really
matter too much whether it's with or without brackets. My preference is
without because then you just stick it at the top and don't have an
extra level of
Can't both (brackets and non) be supported? I have some sick people in
my own company that would LOVE if they could embed multiple namespaces
in the same file. In circles around my own cubicle, engineers prefer
to write one class per namespace, per file, as God intended. Various
Perl,
On 26.03.2008 03:55, Christian Schneider wrote:
Playing around with PHP 6 I noticed that some functions start to
complain about conversion of null values to strings:
php -d error_reporting=65535 -r 'var_dump(urldecode(null));'
Warning: urldecode() expects parameter 1 to be strictly a
Hello Andi,
Wednesday, March 26, 2008, 7:12:18 AM, you wrote:
In general I'd prefer one namespace per-file, at least as a best
practice and common advertised use. For this case it doesn't really
matter too much whether it's with or without brackets. My preference is
without because then you
On Thu, Mar 20, 2008 at 2:45 AM, Rasmus Lerdorf [EMAIL PROTECTED] wrote:
Gwynne Raskind wrote:
My two US cents :).
On Mar 19, 2008, at 9:17 PM, Jani Taskinen wrote:
Here is a quick run down of some of the features of CMake and tools
associated with it:
• A single configure
On Thu, Mar 20, 2008 at 5:29 PM, Cristian Rodriguez
[EMAIL PROTECTED] wrote:
2008/3/19, Scott MacVicar [EMAIL PROTECTED]:
Another alternative would be to simply bundle CMake with PHP,
Nope, Cmake is available in almost all distributions and in the case
some of them dont have it yet,
Pierre Joye wrote:
On Tue, Mar 4, 2008 at 3:17 PM, Christian Schneider
[EMAIL PROTECTED] wrote:
playing around with PHP 6 I noticed the following BC issue:
floatval(4.2foo) gives an E_NOTICE A non well formed numeric value
encountered. The type casting (float)4.2foo still works as before.
Hello Gregory,
+ for (p = ptr; isalnum((int)*p) || *p == '+' || *p == '-' || *p
== '.'; p++);
+ /* p - ptr 1 allows us to skip things like C:\whatever */
+ if ((*p == ':') (p - ptr 1) (path_len - (p - path) 2)
(p[1] == '/') (p[2] == '/')) {
+
On Wed, Mar 26, 2008 at 12:27 PM, Christian Schneider
[EMAIL PROTECTED] wrote:
Pierre Joye wrote:
On Tue, Mar 4, 2008 at 3:17 PM, Christian Schneider
[EMAIL PROTECTED] wrote:
playing around with PHP 6 I noticed the following BC issue:
floatval(4.2foo) gives an E_NOTICE A non well
Em Qua, 2008-03-26 às 12:55 +0100, Pierre Joye escreveu:
I don't see why it has been bogufied. It should be either fixed (as
you described) or the documentation has to be updated (move the bug to
the doc category).
Which # is it?
Re-opened. http://bugs.php.net/bug.php?id=44533
--
Regards,
Hello,
I would like know which itens below needs be backported to 5_3:
- Added runtime JIT auto-globals fetching and caching. (Dmitry, Sara)
- Added jump label operator (limited goto). (Dmitry, Sara)
- Removed support for continue and break operators with non-constant
operands. (Dmitry)
-
Hi!
- Added runtime JIT auto-globals fetching and caching. (Dmitry, Sara)
Does this change any semantics, etc? Any reason why it wasn't merged in
the first place?
- Added jump label operator (limited goto). (Dmitry, Sara)
No strong opinion here, I didn't need it anyway :)
- Removed
On 25/03/2008, Felipe Pena [EMAIL PROTECTED] wrote:
Em Ter, 2008-03-25 às 12:35 +0100, Lars Strojny escreveu:
Would that mean that the following code does not work anymore?
?php
class Foo
{
protected function method()
{
}
public function
On Fri, 21 Mar 2008, Stanislav Malyshev wrote:
But maybe the change is that now it is considered evil by an even larger
amount of people.
So far I saw four. I do not double I can find 5 people that like templates
with short tags.
I don't think I've ever said I don't like short tags. It's
On Sun, 23 Mar 2008, Tex Texin wrote:
Pierre, Marcus, et al.
1) The project started a year or so ago. A few of us from different
companies had a strong need to see that PHP had international
collation, formats, normalization, grapheme support, and other
functions in a time frame nearer
On Sun, 23 Mar 2008, Steph Fox wrote:
Few people want this extension to be moved to core, which means: every
decision about this extension is deciding anything about PHP.
Those 'few people' were actually in the majority when it was put to the vote.
Yes development could and should've been
On Sun, 23 Mar 2008, Stanislav Malyshev wrote:
Noone is arguing about the usefulness of the extension.
We are arguing about how the maintainers of the extension are about to
abandon it once it reaches -stable and the fact it doesn't even try to
Hannes, wtf you are talking about? Nobody
On Sun, 23 Mar 2008, Lester Caine wrote:
Derick Rethans wrote:
On Fri, 21 Mar 2008, Pierre Joye wrote:
I rather prefer to have this class (and related) within the ext/date
extensions. It is the only way to have a consistent and working
date/time API in php. Date/time formatting is
On 3/26/08, Richard Quadling [EMAIL PROTECTED] wrote:
Shouldn't the instance be the limiting factor?
it shouldn't
public/protected/private are related to classes, not to objects.
--
Alexey Zakhlestin
http://blog.milkfarmsoft.com/
--
PHP Internals - PHP Runtime Development Mailing List
To
2008/3/26, Stanislav Malyshev [EMAIL PROTECTED]:
- Removed support for continue and break operators with non-constant
operands. (Dmitry)
I'd wait for 6 with this. May break some scripts.
I dont think it will break more a piece of code that doesnt really work. ;)
--
If debugging is
On Wed, Mar 26, 2008 at 5:39 PM, Stanislav Malyshev [EMAIL PROTECTED] wrote:
Hi!
- Added runtime JIT auto-globals fetching and caching. (Dmitry, Sara)
Does this change any semantics, etc? Any reason why it wasn't merged in
the first place?
It was initially done for the input encoding
On 3/26/08, Richard Quadling [EMAIL PROTECTED] wrote:
It just doesn't seem right to be able to call a private or protected
method of another instance. Sort of isn't private any more.
And as for being able to call a protected method of a completely
different class, just because it shares
I'd wait for 6 with this. May break some scripts.
I dont think it will break more a piece of code that doesnt really work. ;)
Af far as I know, breaks with arguments do work in PHP.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN:
Hello Alexey,
Wednesday, March 26, 2008, 6:05:12 PM, you wrote:
On 3/26/08, Richard Quadling [EMAIL PROTECTED] wrote:
It just doesn't seem right to be able to call a private or protected
method of another instance. Sort of isn't private any more.
And as for being able to call a
I've developed the patch listed in http://bugs.php.net/44393 over the last
few weeks, and I just thought I'd try to solicit some feedback. It's an
enhancement to the Windows ISAPI module which allows Keep-Alive connections
and chunked content-encoding. I'd sure love to get this incorporated into
Marcus Boerger wrote:
language out there that is in use and has anything like that. And even more
scary to me, you did not solve anything by this because people still could
write code prior to the namespace keyword. So no matter what we are screwed
?
[EMAIL PROTECTED]:~/workspace/php5$ cat
I am not so sure. I see (in the feb-04 sources) just collator,
formatter, locale, msgformat and normalizer - and dateformatter that
should be integrated into the Date extension to avoid issues and
confusion.
I'm all for integrating it in PHP 6, however I do not see how it is
possible to do
Which # is it?
Re-opened. http://bugs.php.net/bug.php?id=44533
So it's just gives additional notice? That's a bit strange since intval
doesn't, and neither does (float). I see no reason for floatval() to be
different from others.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL
Hi!
I don't think I've ever said I don't like short tags. It's not the issue
here. The issue is that allowing to change it during runtime adds more
WTF to PHP. WTF factors are bad.
OK, there were people saying short tags are mortal sin, devil's device
to lure pure souls into the hell and
On Wed, Mar 26, 2008 at 8:29 PM, Stanislav Malyshev [EMAIL PROTECTED] wrote:
I am not so sure. I see (in the feb-04 sources) just collator,
formatter, locale, msgformat and normalizer - and dateformatter that
should be integrated into the Date extension to avoid issues and
confusion.
Marcus Boerger wrote:
Hello Gregory,
+ for (p = ptr; isalnum((int)*p) || *p == '+' || *p == '-' ||
*p == '.'; p++);
+ /* p - ptr 1 allows us to skip things like C:\whatever */
+ if ((*p == ':') (p - ptr 1) (path_len - (p - path)
2) (p[1] ==
Hi!
As intl will requires it, why is it unacceptable?
intl is specialized extension for people dealing with global
environments. It will be enabled only by people that really need it.
ext/date is much more general-purpose function, used by thousands of
applications that don't care at all
This still will works.
Surely it shouldn't work at all unless the $foo === $this?
Why not? If the context is right, why shouldn't it be able to call this
content's protected functions?
As I understand, protected funciton means no code outside the class can
call it, since it's not a part of
It just doesn't seem right to be able to call a private or protected
method of another instance. Sort of isn't private any more.
Why not? Private/protected is meant to separate APIs, it's not a
security check on objects. Private means this API belongs to this class
only, protected means this
OK, let's back to the topic, is there any conclusion on this topic yet?
I certainly would like not to miss the release of 5.3 and ready to help
with any issue.
As to user request, here is one :-)
http://bugs.php.net/bug.php?id=42987
According to this ticket, this has been assigned to
Hi!
According to this ticket, this has been assigned to johannes, should I
follow up with this ticket to get it going?
Johannes is the RM for 5.3, so he decides if/when it gets in. :)
Our LSAPI library code has been license under BSD license, and there are
If extension and library are
On Wed, Mar 26, 2008 at 8:55 PM, Stanislav Malyshev [EMAIL PROTECTED] wrote:
Hi!
I don't think I've ever said I don't like short tags. It's not the issue
here. The issue is that allowing to change it during runtime adds more
WTF to PHP. WTF factors are bad.
OK, there were people
Hi,
On Wed, Mar 26, 2008 at 9:02 PM, Stanislav Malyshev [EMAIL PROTECTED] wrote:
Hi!
As intl will requires it, why is it unacceptable?
intl is specialized extension for people dealing with global
environments. It will be enabled only by people that really need it.
ext/date is much
On 26.03.2008, at 20:55, Stanislav Malyshev wrote:
Hi!
I don't think I've ever said I don't like short tags. It's not the
issue here. The issue is that allowing to change it during runtime
adds more WTF to PHP. WTF factors are bad.
2. For any code messing with this value - and this
You do know that having short tags enabled will result in a parse
error in the following situation, right?:
Yes, I do know. In fact, I mentioned this knowledge in virtually every
email on the subject. Your point being?
idea ever - but I still think it'll just create more wtf then
necessary.
Hi!
do note that we have increasingly large numbers of way to jump out of
the scope (exceptions, recoverable errors). this obviously makes these
kinds of cleanups potentially easier to forget.
You'd need to catch and process exceptions anyway, and recoverable
errors, as far as I understand,
Hi!
This feature can then be optional in ext/date. That should not be an
issue for those not willing to use a reliable date formatting system
as they are certainly not interested in intl either.
I think making it optional in ext/date would be harder. On top of that,
optional functions in
On Wed, Mar 26, 2008 at 9:25 PM, Stanislav Malyshev [EMAIL PROTECTED] wrote:
I will repeat it as many times as necessary:
1. This situation can happen only if you have written very buggy
template code - there exists no such code right now and one has to be
rather sloppy to create such
On Wed, Mar 26, 2008 at 9:39 PM, Hannes Magnusson
[EMAIL PROTECTED] wrote:
On Wed, Mar 26, 2008 at 9:25 PM, Stanislav Malyshev [EMAIL PROTECTED] wrote:
I will repeat it as many times as necessary:
1. This situation can happen only if you have written very buggy
template code - there
Hi,
Hannes Magnusson wrote:
?php
$foo = 2;
while(true) {
while(true) {
echo Hello world!\n;
if (true) {
break $foo;
}
}
echo Never reached\n;
}
This is what was removed. not normal break 2;
On Wed, Mar 26, 2008 at 9:38 PM, Stanislav Malyshev [EMAIL PROTECTED] wrote:
Hi!
This feature can then be optional in ext/date. That should not be an
issue for those not willing to use a reliable date formatting system
as they are certainly not interested in intl either.
I think
Hi!
I meant to duplicate the code from ext/date (where it belongs) in
pecl/intl. Please notice the pecl/intl not php-src/ext. The goal is
to provide the DateFormatter feature to php 5.2 users.
Great, right now 5.2 users can use intl extension from pecl, including
DateFormatter.
As Derick
Hi!
if (true) {
break $foo;
}
As I understand, this code works now.
never heard of XPath.class.php and also never heard of some code
deep inside this Xayara CMS.
And used by people. Did I or anybody here on the list actually contacted
with these people or not
Richard Krehbiel kirjoitti:
I've developed the patch listed in http://bugs.php.net/44393 over the last
few weeks, and I just thought I'd try to solicit some feedback. It's an
enhancement to the Windows ISAPI module which allows Keep-Alive connections
and chunked content-encoding. I'd sure love
On 26.03.2008, at 22:05, Stanislav Malyshev wrote:
never heard of XPath.class.php and also never heard of some
code deep inside this Xayara CMS.
And used by people. Did I or anybody here on the list actually
contacted with these people or not does not matter - we can't
contact millions
-Original Message-
From: Derick Rethans [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 26, 2008 9:49 AM
To: Tex Texin
Cc: Marcus Boerger; Pierre Joye; [EMAIL PROTECTED]; PHP Developers Mailing List
Subject: RE: [PHP-DEV] Re: [php-icu] Graphemes and unicode vs intl extension
On Sun,
On Wed, Mar 26, 2008 at 10:22 PM, Tex Texin [EMAIL PROTECTED] wrote:
Hi Tex,
I understand the concern, but it is really a quite theoretical concern.
The intl extension is a PHP wrapper around ICU API. The code layer is very
thin.
This theoretical concern is actually how we work. It does
Hello Tex,
Wednesday, March 26, 2008, 10:22:33 PM, you wrote:
-Original Message-
From: Derick Rethans [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 26, 2008 9:49 AM
To: Tex Texin
Cc: Marcus Boerger; Pierre Joye; [EMAIL PROTECTED]; PHP Developers Mailing
List
Subject: RE:
Hello Hannes,
Wednesday, March 26, 2008, 9:41:31 PM, you wrote:
On Wed, Mar 26, 2008 at 9:39 PM, Hannes Magnusson
[EMAIL PROTECTED] wrote:
On Wed, Mar 26, 2008 at 9:25 PM, Stanislav Malyshev [EMAIL PROTECTED]
wrote:
I will repeat it as many times as necessary:
1. This situation can
Am 26.03.2008 um 20:48 schrieb Stanislav Malyshev:
Which # is it?
Re-opened. http://bugs.php.net/bug.php?id=44533
So it's just gives additional notice? That's a bit strange since
intval doesn't, and neither does (float). I see no reason for
floatval() to be different from others.
I
-Original Message-
From: Stanislav Malyshev [mailto:[EMAIL PROTECTED]
Sent: 26 March 2008 20:28
To: Lukas Kahwe Smith
Cc: Derick Rethans; Marcus Boerger; Hannes Magnusson; PHP Internals
Subject: Re: [PHP-DEV] short_open_tag
Hi!
do note that we have increasingly large
2008/3/26, Stanislav Malyshev [EMAIL PROTECTED]:
- Changed instanceof and catch operators, is_a() and
is_subclass_of() functions to not call __autoload(). (Dmitry)
This definitely should be - there's absolutely no reason any kind on
instanceof-like operator would call autoload.
Hehe,
Hi,
On Wed, 2008-03-26 at 16:07 -0400, George Wang wrote:
OK, let's back to the topic, is there any conclusion on this topic yet?
I certainly would like not to miss the release of 5.3 and ready to help
with any issue.
I think it makes sense, you, as the server's vendor, supports it and
On Wed, 2008-03-26 at 10:04 -0300, Felipe Pena wrote:
Hello,
I would like know which itens below needs be backported to 5_3:
- Added runtime JIT auto-globals fetching and caching. (Dmitry, Sara)
Not sure if this has benefits without the encoding stuff which is
planned for PHP 6.
- Added
On Tue, 2008-03-25 at 23:35 -0700, Paul Chandler wrote:
Can't both (brackets and non) be supported?
NO! This just creates confusion.
johannes
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi!
No offense, but I do think that you may have won more contributors (I
wonder if it was even necessary given the amount of committers I saw)
if you were discussing the project on php-18n and called for help
earlier. I18n is a very important missing piece of PHP.
What part of announced in
Hi,
On Fri, 2008-03-21 at 22:36 +0100, Marcus Boerger wrote:
we all were asked to stop discussing syntax of namespaces as we were told
that we would decide after the namespace functionality was fully implemented.
Now I think that the functionallity is pretty much settled we should
revisit
On Thu, Mar 27, 2008 at 12:38 AM, Stanislav Malyshev [EMAIL PROTECTED] wrote:
Actually there is something hazardous to find, why this private list?
To have actually some work done, as opposed to refuting never-ending
stream of conspiracy theories.
Only you have seen our complains as a
On Thu, Mar 27, 2008 at 12:34 AM, Johannes Schlüter [EMAIL PROTECTED] wrote:
On Wed, 2008-03-26 at 10:04 -0300, Felipe Pena wrote:
Hello,
I would like know which itens below needs be backported to 5_3:
- Added runtime JIT auto-globals fetching and caching. (Dmitry, Sara)
Not
On Thu, 2008-03-27 at 00:48 +0100, Pierre Joye wrote:
On Thu, Mar 27, 2008 at 12:34 AM, Johannes Schlüter [EMAIL PROTECTED] wrote:
On Wed, 2008-03-26 at 10:04 -0300, Felipe Pena wrote:
Hello,
I would like know which itens below needs be backported to 5_3:
- Added
On Thu, Mar 27, 2008 at 12:54 AM, Johannes Schlüter [EMAIL PROTECTED] wrote:
And compile time JIT is fine as long as we don't have to care for
encoding, right? So this change won't be needed in 5.3.
Except when one sends a xxMB post that you are not expecting and will
not use. But that has
On Thu, 2008-03-27 at 01:01 +0100, Pierre Joye wrote:
On Thu, Mar 27, 2008 at 12:54 AM, Johannes Schlüter [EMAIL PROTECTED] wrote:
And compile time JIT is fine as long as we don't have to care for
encoding, right? So this change won't be needed in 5.3.
Except when one sends a xxMB
On Thu, Mar 27, 2008 at 1:05 AM, Johannes Schlüter [EMAIL PROTECTED] wrote:
On Thu, 2008-03-27 at 01:01 +0100, Pierre Joye wrote:
On Thu, Mar 27, 2008 at 12:54 AM, Johannes Schlüter [EMAIL PROTECTED]
wrote:
And compile time JIT is fine as long as we don't have to care for
On Wed, March 26, 2008 12:13 pm, Stanislav Malyshev wrote:
I'd wait for 6 with this. May break some scripts.
I dont think it will break more a piece of code that doesnt really
work. ;)
Af far as I know, breaks with arguments do work in PHP.
And I even used it once...
I could re-factor to
On Mon, March 24, 2008 8:16 pm, Felipe Pena wrote:
Do we keep the support added in http://bugs.php.net/bug.php?id=37632
(that isn't supported in C++, for instance) or fix the
zend_is_callable_check_func() ?
Personally, it makes sense to me for a PROTECTED function (et al) with
a common
2008/3/26, Johannes Schlüter [EMAIL PROTECTED]:
- Added jump label operator (limited goto). (Dmitry, Sara)
No objection, while it adds yet another keyword.
Patch:
- http://felipe.ath.cx/diff/goto.diff
Patch full (with re2c regenerated files):
-
2008/3/26, Johannes Schlüter [EMAIL PROTECTED]:
- Removed undocumented and incomplete support for strings in list()
operator. (Dmitry)
What exactly does that change?
$a = foo; list($b) = $a; var_dump($b);
Before:
string(1) f
After (HEAD):
NULL
--
PHP Internals - PHP Runtime
72 matches
Mail list logo
