On Sun, Oct 12, 2014 at 12:36 PM, Zeev Suraski wrote:
>
> For the record, I don't feel strongly about # comments, but I do think that
> we should have good reasons to actually *remove* features that are better
> than "this is how it's done". Valid reasons can be performance penalties of
> keepin
On Mon, 2014-10-13 at 02:45 +0200, Marco Pivetta wrote:
> The point is removing more API from core and moving it to userland.
> API implemented in core needs to be maintained by core devs, and is
> non-transparent to consumers (reflection/debugging/etc).
> In general, I've always been against any n
On 12 October 2014 00:47, Andrea Faulds wrote:
>
> On 11 Oct 2014, at 23:42, Rowan Collins wrote:
>
> > func_get_args() and func_num_args(), OTOH, existed solely to support
> variadics, and anything taking advantage of them being functions rather
> than a language structure would have to be quit
On 12/10/2014 11:11, Nikita Popov wrote:
For example, things like this:
>
> # style comments in ini files (since PHP 5.3)
>
>I don't think we should remove at all (or why is this even deprecated?!
>
Because ini files use ; for comments and not #.
I was curious enough about this to dig into so
Hi Andrea,
> Allowing # for comments stops you from using # in string property values.
>
> Though I'm not sure why you'd need to.
That will be the case for any character to use for comments. Uses ;
for comments will stop you from using it in values.
Regards.
--
Yannick K.
--
PHP Internals - P
On 12 Oct 2014, at 11:36, Zeev Suraski wrote:
> For the record, I don't feel strongly about # comments, but I do think that
> we should have good reasons to actually *remove* features that are better
> than "this is how it's done". Valid reasons can be performance penalties of
> keeping the fea
> -Original Message-
> From: Nikita Popov [mailto:nikita@gmail.com]
> Sent: Sunday, October 12, 2014 1:11 PM
> To: Derick Rethans
> Cc: PHP internals
> Subject: Re: [PHP-DEV] [RFC] Remove deprecated functionality in PHP 7
>
> On Sun, Oct 12, 2014 at 9:56 AM, Derick Rethans wrote:
>
> >
I think there should be a little bit more voting "options" - or rather
categories.
For example, things like this:
# style comments in ini files (since PHP 5.3)
I don't think we should remove at all (or why is this even deprecated?!
Because ini files use ; for comments and not #.
Nikita
On Sun, Oct 12, 2014 at 9:56 AM, Derick Rethans wrote:
> On Sat, 11 Oct 2014, Nikita Popov wrote:
>
> > Hi internals!
> >
> > We currently have a number of deprecated features, which we likely want
> to
> > remove in PHP 7. I've created a tracking RFC listing deprecated
> > functionality (if I mi
On Sun, Oct 12, 2014 at 10:37 AM, Robert Stoll wrote:
> Hey,
>
>
>
> I just stumbled over a method call of a non-static method with self and
> was asking myself again, why does PHP support
> this behaviour. An example to outline what I am writing of:
>
>
>
> class A{
>
> function foo(){
>
>
> In your given example, $this is defined when A::bar() is called;
> interestingly, when this class is extended it will
still only call
> A::bar() as opposed to calling $this->bar(). Whether this is useful behaviour
> is irrelevant :)
>
Right, I completely forgot that. So calling it with self
On 12 Oct 2014, at 16:37, Robert Stoll wrote:
> Hey,
>
>
>
> I just stumbled over a method call of a non-static method with self and was
> asking myself again, why does PHP support
> this behaviour. An example to outline what I am writing of:
>
>
>
> class A{
>
> function foo(){
>
>
Hey,
I just stumbled over a method call of a non-static method with self and was
asking myself again, why does PHP support
this behaviour. An example to outline what I am writing of:
class A{
function foo(){
self::bar();
}
function bar(){}
}
IMO it should not be allowed
On Oct 12, 2014 12:54 AM, "Derick Rethans" wrote:
>
> On Sat, 11 Oct 2014, Kris Craig wrote:
>
> > On Oct 11, 2014 1:52 PM, "Nikita Popov" wrote:
> > >
> > > We currently have a number of deprecated features, which we likely
> > > want to remove in PHP 7. I've created a tracking RFC listing
> > >
On 12/10/14 01:13, Rasmus Lerdorf wrote:
> Keep in mind though that it would be mostly symbolic. The majority of users
> get their PHP and extensions from distros. And distros have been separating
> out core-bundled extensions for a decade now. Users have absolutely no idea
> whether their php-m
On Sat, 11 Oct 2014, Nikita Popov wrote:
> Hi internals!
>
> We currently have a number of deprecated features, which we likely want to
> remove in PHP 7. I've created a tracking RFC listing deprecated
> functionality (if I missed something, please tell):
>
> https://wiki.php.net/rfc/remove_
On Sat, 11 Oct 2014, Kris Craig wrote:
> On Oct 11, 2014 1:52 PM, "Nikita Popov" wrote:
> >
> > We currently have a number of deprecated features, which we likely
> > want to remove in PHP 7. I've created a tracking RFC listing
> > deprecated functionality (if I missed something, please tell):
On 12/10/14 02:15, Rowan Collins wrote:
> On 11/10/2014 10:13, Lester Caine wrote:
>> BIGINT is the SQL99-compliant 64-bit signed integer type
>
> It's a matter of context. In C, and therefore in related discussions
> (which includes the internals of PHP), integers are referred to as
> "short" (fo
18 matches
Mail list logo
