On 04/18/2012 11:04 PM, Stas Malyshev wrote:
Hi!
default is already a reserved keyword. It's used in switch
constructs. So it is safe to use :)
Ah, silly me, indeed it is. Then I guess it doesn't hurt to add it as an
option. Will do.
I can't estimate the amount of breakage, but what
Hi!
I can't estimate the amount of breakage, but what about using underscore
(literal _) without quotation marks?
This one is taken. See: http://us2.php.net/_
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
--
PHP Internals - PHP Runtime
Hi!
If there is no other discussion for this, I'd like to move this to the voting
phase, any objects?
https://wiki.php.net/rfc/propertygetsetsyntax-as-implemented
Sorry, I didn't have time to look into it yet (yes I know it was around
for a long time...) in detail. From the quick glance I
Hi!
In summary: should abstract protected constructors be inaccessible by
siblings, as is true of __clone and __destruct? Should __construct, __clone
and __destruct always be accessible in relatives, as is true of other
methods? Depending on the answers, there could be a documentation issue,
Hi,
Are the dashes acceptable or undesirable?
I think without dashes it is more in line with other keywords, like
instanceof or insteadof.
Because keywords are not case sensitive, one who likes them to be more readable
could write them camelCased, for example readOnly, or writeOnly.
--
Hi,
This post is about bug #18556 (https://bugs.php.net/bug.php?id=18556)
which is a decade old.
As the recent comments on that page indicate, there's not a
deterministic way to resolve this issue, apart from eliminating
tolower() calls for function/class names during lookup. Hence totally
2012/4/20 Stas Malyshev smalys...@sugarcrm.com:
How these would work with isset - what !empty($this-Hours) return? What
would happen if you do unset($this-Hours)? What happens if you do
$this-Hours++ or sort($this-Hours) (assuming $Hours is an array)?
These things need to be defined in the RFC
On 2012-04-20, Christoph Hochstrasser christoph.hochstras...@gmail.com wrote:
Hi,
Are the dashes acceptable or undesirable?
I think without dashes it is more in line with other keywords, like
instanceof or insteadof.
Because keywords are not case sensitive, one who likes them to be more
On 2012-04-20, C.Koy can5...@gmail.com wrote:
This post is about bug #18556 (https://bugs.php.net/bug.php?id=18556)
which is a decade old.
As the recent comments on that page indicate, there's not a
deterministic way to resolve this issue, apart from eliminating
tolower() calls for
Yup - a one time transition would be preferable to that.
On Fri, Apr 20, 2012 at 9:13 AM, Matthew Weier O'Phinney
weierophin...@php.net wrote:
On 2012-04-20, C.Koy can5...@gmail.com wrote:
This post is about bug #18556 (https://bugs.php.net/bug.php?id=18556)
which is a decade old.
As the
In past years such switches where deprecated and removed (in 5.3 most of
them, in 5.4 finally all that stuff is gone for good). So any solution,
involving a switch that modifies how code is executed will hit a wall of
resistance. It's the lesson that was learned the hard way.
So it may be the
On Fri, Apr 20, 2012 at 12:20 PM, C.Koy can5...@gmail.com wrote:
Hi,
This post is about bug #18556 (https://bugs.php.net/bug.php?id=18556) which
is a decade old.
As the recent comments on that page indicate, there's not a deterministic
way to resolve this issue, apart from eliminating
Because you can write a function name, say, in Cyrilic and it will just
work.
20 апреля 2012 г. 16:47 пользователь Nikita Popov nikita@googlemail.com
написал:
On Fri, Apr 20, 2012 at 12:20 PM, C.Koy can5...@gmail.com wrote:
Hi,
This post is about bug #18556
Because you can write a function name, say, in Cyrilic and it will just work.
PHP deals with strings on a binary level though. To PHP a function
name of Áãç, for example is just a set of 256 bit encoded bytes. So
\xc3\x81\xc3\xa3\xc3\xa7 is all it sees, right? I'm not sure I
follow what the
On Fri, Apr 20, 2012 at 9:01 AM, Sherif Ramadan theanomaly...@gmail.comwrote:
Because you can write a function name, say, in Cyrilic and it will just
work.
PHP deals with strings on a binary level though. To PHP a function
name of Áãç, for example is just a set of 256 bit encoded bytes.
On Fri, 2012-04-20 at 09:21 -0400, Tom Boutell wrote:
Yup - a one time transition would be preferable to that.
Then the question is: Why? What's the benefit from a break? Is there a
need to have imagecreatefrompng() next to a ImageCreateFromPNG()? Or is
the reason to be a tiny bit faster? Or is
But in order to be case insensitive, PHP needs to know that strtolower(A)
== 'a'. So if you use Cyrilic for userland functions/classes, php needs a
cyrillic aware strtolower function. Then the problem is that core
classes/functions need to use a plain ASCII strtolower for case
insensitivity.
On 4/20/2012 6:44 PM, Sherif Ramadan wrote:
Its naming rules are a little bit inconsistent in that regard. I just
don't see a point in making it completely locale aware. The fact that
you can do soefunc() and SOMEFUNC() and still invoke the same function
is a benefit. And I suppose for those
On Fri, Apr 20, 2012 at 8:44 AM, Sherif Ramadan theanomaly...@gmail.comwrote:
But in order to be case insensitive, PHP needs to know that
strtolower(A)
== 'a'. So if you use Cyrilic for userland functions/classes, php needs a
cyrillic aware strtolower function. Then the problem is that
On 2012-04-20, Kris Craig kris.cr...@gmail.com wrote:
On Fri, Apr 20, 2012 at 8:44 AM, Sherif Ramadan theanomaly...@gmail.com
wrote:
But in order to be case insensitive, PHP needs to know that
strtolower(A) == 'a'. So if you use Cyrilic for userland
functions/classes, php needs a
Could you elaborate? Aside from making PHP forgiving of typos and overall
laziness on the part of the coder, and of course BC notwithstanding, I'm not
sure I understand what benefit there is to preserving this inconsistent
behavior.
Kris,
Sorry, first to be clear I made a typo there, but
On 4/20/2012 8:57 PM, Kris Craig wrote:
Turkish localization notwithstanding (I confess that I know absolutely *
nothing* about that lol), one possible use-case could be if you're
including an external library/framework that contains a function with the
same name but different case. I'm not
On 4/20/2012 9:48 PM, C.Koy wrote:
Java, C#, Python, Ruby... are all case-sensitive. This is not a feature
to be (mis-)used so that one can have a function named myfunc() and
MyFunc() in the same code base.
Case-insensitive class/function/interface names is a confusion for
everyone with non-PHP
Hi there,
Out of curiosity, how would one migrate a codebase for full case
sensitivity in PHP? They would need to rewrite their calls of core
functions, plus PECL functions. Those are easy enough to spot, but there
are also custom extensions. True, one could maybe parse the .h files to get
the
On 04/20/2012 08:48 PM, C.Koy wrote:
On 4/20/2012 8:57 PM, Kris Craig wrote:
Turkish localization notwithstanding (I confess that I know absolutely *
nothing* about that lol), one possible use-case could be if you're
including an external library/framework that contains a function with the
On Sat, 2012-04-21 at 01:16 +0200, Stefan Neufeind wrote:
I think we might possibly add a
special kind of deprecation where the non-matching case would still
work but (if you activate those deprecation-warnings) would trigger
warnings so you can clean up your code.
yay - two lookups instead
On Fri, Apr 20, 2012 at 3:20 AM, C.Koy can5...@gmail.com wrote:
As the recent comments on that page indicate, there's not a deterministic
way to resolve this issue, apart from eliminating tolower() calls for
function/class names during lookup. Hence totally case-sensitive PHP.
What about
27 matches
Mail list logo
