@Rasmus:
I don't see what's the problem of aliasing functions for the next 1-2
majors, deprecate the inconsistent one in the following and remove later.
On Wed, Mar 4, 2015 at 10:33 AM, Trevor Suarez ric...@gmail.com wrote:
... well that's a constructive way of going about it. I don't think
-Ursprüngliche Nachricht-
Von: Philip Sturgeon [mailto:pjsturg...@gmail.com]
Gesendet: Mittwoch, 4. März 2015 16:49
An: Robert Stoll
Cc: PHP Internals
Betreff: Re: [PHP-DEV] [RFC] Anonymous Classes
On Tue, Mar 3, 2015 at 12:03 PM, Robert Stoll p...@tutteli.ch wrote:
Hi Philip
On 03/03/2015 07:34 PM, Yasuo Ohgaki wrote:
Hi Michael,
On Wed, Mar 4, 2015 at 12:15 PM, Michael Schuett michaeljs1...@gmail.com
wrote:
Your evaluation is pretty anecdotal. I agree with some points but you need
some solid evidence if you are going to rate these languages. Also do you
On Tue, Mar 3, 2015 at 12:03 PM, Robert Stoll p...@tutteli.ch wrote:
Hi Philip
-Ursprüngliche Nachricht-
Von: Philip Sturgeon [mailto:pjsturg...@gmail.com]
Gesendet: Dienstag, 24. Februar 2015 14:52
An: PHP Internals
Betreff: [PHP-DEV] [RFC] Anonymous Classes
Good day!
Am 04.03.2015 um 09:52 schrieb Nikita Popov:
So, tl;dr: I think the patch is too risky. Even if we can make sure that
we've covered all the current edge-cases and don't regress anything, I'm
afraid that this will cause complications with future changes. This ends up
replicating too many
On Wed, Mar 4, 2015 at 10:24 AM Rasmus Lerdorf ras...@lerdorf.com wrote:
Yasuo, please stop. This isn't going to happen. Changing strlen() to
str_len() is just ridiculous. -Rasmus
Trevor Suarez wrote on 04/03/2015 15:33:
... well that's a constructive way of going about it. I don't think
On 04/03/15 17:03, Rowan Collins wrote:
so if you're looking for something constructive, help move those ideas
forward, rather than flogging the dead horse.
The extensive changes documented in this RFC are well over the top, but
a much better approach would be to identify blocks which do allow
On 03/04/2015 08:26 AM, guilhermebla...@gmail.com wrote:
@Rasmus:
I don't see what's the problem of aliasing functions for the next 1-2
majors, deprecate the inconsistent one in the following and remove later.
As far as I am concerned str_len() would be the inconsistent one. Like I
explained
On 3/4/15 9:03 AM, Rowan Collins wrote:
On Wed, Mar 4, 2015 at 10:24 AM Rasmus Lerdorf ras...@lerdorf.com wrote:
Yasuo, please stop. This isn't going to happen. Changing strlen() to str_len()
is just ridiculous. -Rasmus
Trevor Suarez wrote on 04/03/2015 15:33:
... well that's a
Hi
2015-03-04 5:52 GMT-03:00 Nikita Popov nikita@gmail.com:
After reviewing the implementation, I've decided to vote no on this RFC.
I had originally assumed that if this proposal is limited to method names
and class constants only the implementation should be pretty simple and
robust.
Hi,
2015-03-03 16:48 GMT-03:00 Yasuo Ohgaki yohg...@ohgaki.net:
Hi Marcio,
I understand your reasons. Compatibility is important, but detecting
function body contents and
suppressing errors by engine is too hacky. Raising E_DEPRECATE/E_STRICT by
function definition seems
the way to go.
Hi Rowan,
On Wed, Mar 4, 2015 at 6:16 PM, Rowan Collins rowan.coll...@gmail.com
wrote:
Several of the costs I listed are for new users, and several will continue
indefinitely if we don't remove the old names, and are therefore long term.
Could you be more explicit in the benefits you see?
Hi Leigh,
On Thu, Mar 5, 2015 at 4:30 AM, Leigh lei...@gmail.com wrote:
On 1 March 2015 at 11:29, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Thoughts?
require 'function_aliases.php'; // End of discussion.
Maintain it however you want, set it up as a composer package,
whatever. Absolutely
... well that's a constructive way of going about it. I don't think Yasuo
did anything harmful or rude in making his proposal. Regardless of how
realistic the idea may be, I don't think its ever appropriate or
constructive to tell someone to simply stop because something is just
ridiculous.
On
On 1 March 2015 at 11:29, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Thoughts?
require 'function_aliases.php'; // End of discussion.
Maintain it however you want, set it up as a composer package,
whatever. Absolutely no reason for this to be in core, and absolutely
not worth the trouble it
Hi Michael,
On Wed, Mar 4, 2015 at 12:58 PM, Michael Schuett michaeljs1...@gmail.com
wrote:
So i find this kind of odd since you use err every other place in bz. but
this is a minor nitpick.
- bz_error → bzerror
- bz_error_str → bzerrstr
Overall I fell this change would be nice for
Leigh wrote:
On 1 March 2015 at 11:29, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Thoughts?
require 'function_aliases.php'; // End of discussion.
It is not possible to my knowledge, however, to define function aliases
in PHP (a wrapper function would have an obvious performance penalty).
On 3/3/15 6:46 PM, Yasuo Ohgaki wrote:
Whether we like it or not, people evaluate languages by matrix like
PHP RubyPython
OO support5 5 5
Flexible syntax 3 5 5
AOP
Hi Marcio,
On Thu, Mar 5, 2015 at 4:07 AM, Marcio Almada marcio.w...@gmail.com wrote:
2015-03-03 16:48 GMT-03:00 Yasuo Ohgaki yohg...@ohgaki.net:
Hi Marcio,
I understand your reasons. Compatibility is important, but detecting
function body contents and
suppressing errors by engine is
Hi Pierre,
On Thu, Mar 5, 2015 at 8:54 AM, Pierre Joye pierre@gmail.com wrote:
On Wed, Mar 4, 2015 at 1:36 PM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi Leigh,
On Thu, Mar 5, 2015 at 4:30 AM, Leigh lei...@gmail.com wrote:
On 1 March 2015 at 11:29, Yasuo Ohgaki yohg...@ohgaki.net
On Wed, Mar 4, 2015 at 1:36 PM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi Leigh,
On Thu, Mar 5, 2015 at 4:30 AM, Leigh lei...@gmail.com wrote:
On 1 March 2015 at 11:29, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Thoughts?
require 'function_aliases.php'; // End of discussion.
Maintain it
On 2 March 2015 at 14:24, Zeev Suraski z...@zend.com wrote:
https://wiki.php.net/rfc/array-to-string (which I voted yes to) deviates
from our guidelines of deprecating features first, and removing them
later;
Should we not go through this deprecation cycle, even if may feel anxious
to get
On 16 January 2015 at 09:16, Nikita Popov nikita@gmail.com wrote:
I'll land the minor removals sometime soon; the unbundling of ext/ereg and
ext/mysql should probably be done by someone else who's more into the PECL
business.
They gone.
Many thanks to Tjerk, for doing all the hard work on
Hi Rowan,
On Thu, Mar 5, 2015 at 10:16 AM, Rowan Collins rowan.coll...@gmail.com
wrote:
On 4 March 2015 21:27:53 GMT, Yasuo Ohgaki yohg...@ohgaki.net wrote:
We cannot remove all issue at once. We are better to adopt incremental
improvement, aren't we?
I think this, more than anything else,
Hi Rasmus,
On Thu, Mar 5, 2015 at 2:14 PM, Rasmus Lerdorf ras...@lerdorf.com wrote:
Every function name defined by IEEE Std 1003.1 along with the arguments
and argument order would be on that list. When we have procedural
functions that are either thin wrappers around or otherwise behave
On 03/04/2015 10:21 PM, Yasuo Ohgaki wrote:
The same could be done for new names.
Manual pages for localtime()/mktime()/etc would look a lot nicer.
I hope there will be more favored developers with the RFC. Since I'm
going to
update manual to have alias search feature, developers used to
Hi all,
On Tue, Mar 3, 2015 at 2:30 AM, Julien Pauli jpa...@php.net wrote:
On Mon, Mar 2, 2015 at 4:10 PM, Patrick ALLAERT patrickalla...@php.net
wrote:
Le lun. 2 mars 2015 à 15:24, Zeev Suraski z...@zend.com a écrit :
All,
https://wiki.php.net/rfc/array-to-string (which I
On 4 March 2015 21:27:53 GMT, Yasuo Ohgaki yohg...@ohgaki.net wrote:
We cannot remove all issue at once. We are better to adopt incremental
improvement, aren't we?
I think this, more than anything else, is where I disagree (having been
persuaded by arguments in previous discussions). Incremental
Hi Dmitry,
On Wed, Mar 4, 2015 at 5:35 PM, Dmitry Stogov dmi...@zend.com wrote:
assert() is not for DbC. It''s useful by it's own. However, new zero-cost
assert() implementation should be reused for true DbC.
I fully agree.
I cannot wait to have it.
Regards,
--
Yasuo Ohgaki
Hi Rasmus,
On Thu, Mar 5, 2015 at 1:46 AM, Rasmus Lerdorf ras...@lerdorf.com wrote:
On 03/04/2015 08:26 AM, guilhermebla...@gmail.com wrote:
@Rasmus:
I don't see what's the problem of aliasing functions for the next 1-2
majors, deprecate the inconsistent one in the following and remove
From: yohg...@gmail.com [mailto:yohg...@gmail.com] On Behalf Of Yasuo Ohgaki,
Sent: Thursday, March 05, 2015 7:21 AM
For example, ctype extension has ctype_ prefix. It replaces
is to ctype_.
we may have isalpha alias as IEEE compliant name. There are many
IEEE confirmed names already. Only
On 03/04/2015 08:25 PM, Yasuo Ohgaki wrote:
Hi Rasmus,
On Thu, Mar 5, 2015 at 1:46 AM, Rasmus Lerdorf ras...@lerdorf.com
mailto:ras...@lerdorf.com wrote:
On 03/04/2015 08:26 AM, guilhermebla...@gmail.com
mailto:guilhermebla...@gmail.com wrote:
@Rasmus:
I don't
Good morning internals!
I would like to propose a small addition be made to the DateTime class.
https://github.com/php/php-src/pull/1145
This is my first contribution to PHP's core, beyond documentation edits.
I'm not sure on the formalities that need to be taken for something like
this to be
Just-In-Time-At-Once JITAO
It is a bit different to the thing we think of as JIT ... new names are
good if old names don't fit ...
Cheers
Joe
On Wed, Mar 4, 2015 at 8:03 AM, Xinchen Hui larue...@php.net wrote:
On Wed, Mar 4, 2015 at 3:44 PM, Dmitry Stogov dmi...@zend.com wrote:
On Tue, Mar
On Wed, Mar 4, 2015 at 3:44 PM, Dmitry Stogov dmi...@zend.com wrote:
On Tue, Mar 3, 2015 at 10:55 PM, Anthony Ferrara ircmax...@gmail.com
wrote:
Dmitry,
So, let's put that to the test, shall we. I compiled and ran the JIT
compiler (can we please stop calling it that, it's not).
This
On Wed, Mar 4, 2015 at 11:21 AM, Joe Watkins pthre...@pthreads.org wrote:
Just-In-Time-At-Once JITAO
file at once, function at once, trace at once, basic block at once - just
different JIT approaches.
The bigger part we analyze at once the more information we may get for
optimization, but the
On 4 March 2015 07:12:41 GMT, Thomas Gielfeldt tho...@gielfeldt.dk wrote:
2015-03-02 16:26 GMT+01:00 Rowan Collins rowan.coll...@gmail.com:
Rowan Collins wrote on 02/03/2015 10:52:
Thomas Gielfeldt wrote on 02/03/2015 07:43:
2015-02-24 17:17 GMT+01:00 Thomas Gielfeldt tho...@gielfeldt.dk:
On 04/03/15 09:41, Rowan Collins wrote:
Hm, yes, I hadn't thought of the use case of sorting external data. Perhaps
we actually need to specify both interfaces (yes, I realise I'm just
inventing more work here, sorry!) - one for the use case of a custom data
structure that wants to worry
On Sun, Mar 1, 2015 at 2:11 AM, Marcio Almada marcio.w...@gmail.com wrote:
Hi,
Since no more issues appeared on discussion, the voting for the Context
Sensitive Lexer is now open. The voting will close in exactly 14 days
counting from now:
RFC:
On 04/03/15 03:34, Yasuo Ohgaki wrote:
I made list of rename candidates
https://wiki.php.net/rfc/consistent_function_names#list_of_functions_to_be_renamed
If you have suggestions, I appreciate!
Taking the starting point ... the coding standard for writing C code for
PHP ... personally I would
On 04/03/15 10:16, Michael Wallner wrote:
While http has been rejected for bundling, it is another example of not
following the C coding standard …
Lester, please stop posting walls of unrelated text. You’re totally off
track. If we’re talking about coding standards, we’re not talking about
On 4 March 2015 00:46:49 GMT, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi Rowan,
On Wed, Mar 4, 2015 at 7:12 AM, Rowan Collins rowan.coll...@gmail.com
wrote:
You are measuring the wrong cost. The cost of adding new names is to
people writing code:
- additional confusion for new users about why
On Tue, Mar 3, 2015 at 10:04 PM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi Dmitry,
On Mon, Mar 2, 2015 at 4:20 PM, Dmitry Stogov dmi...@zend.com wrote:
It may be to late for 7.0.
I feel the same way. It may be better to try add it with 7.x.
Also Alexander liked to to add another
On 04/03/15 00:44, Pierre Joye wrote:
For a php developer point of view, for someone not knowing c or php
internals APIs, I highly recommend https://github.com/phalcon/zephir
Yasuo is pushing function names on the basis of following the coding
standard, but again these secondary tools muddy the
On 04 03 2015, at 09:58, Lester Caine les...@lsces.co.uk wrote:
On 04/03/15 03:34, Yasuo Ohgaki wrote:
I made list of rename candidates
https://wiki.php.net/rfc/consistent_function_names#list_of_functions_to_be_renamed
If you have suggestions, I appreciate!
Taking the starting point ...
45 matches
Mail list logo
