Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76820 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15271 invoked from network); 22 Aug 2014 16:59:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Aug 2014 16:59:05 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.49 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.216.49 mail-qa0-f49.google.com Received: from [209.85.216.49] ([209.85.216.49:38569] helo=mail-qa0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 98/B0-10436-8D677F35 for ; Fri, 22 Aug 2014 12:59:04 -0400 Received: by mail-qa0-f49.google.com with SMTP id dc16so9901521qab.22 for ; Fri, 22 Aug 2014 09:59:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wT7cgegQs6QcGe0S7ZuG0hWwt7pfEoV79dLeScJcQAQ=; b=bVi5EwS0ixf/9BV/CvKAbsdxmoM2+Oo4AhEAcpZivKKCx7TI9YiJPUj4Bb5JPhveuk lDQajhT8JkEZPUugWSjqvd1FFwkKziPD69Qsv8bNO/PgINa8xPuL7ER/LSyP71MfvD6M NltKEhnym1kghMp8Vcu+7JHtg0uBlMQ+mARpZgJNodIpYa2qcO1hOiCQb1ILYj3BX2qb wjuXeHBdxPTNJSXpIbWwtjv9WsPa1M8EY6pzjwZO0lNe9AwltPHgGxhLo9haLd9E6t6K M69cGROGEDNWMC57l1NuvYr+W9kNqo+vauIJQQNeYYrt79BWGBu9g4PLlKVkVQLXXVNY 9fIw== MIME-Version: 1.0 X-Received: by 10.224.114.136 with SMTP id e8mr8911906qaq.67.1408726742044; Fri, 22 Aug 2014 09:59:02 -0700 (PDT) Received: by 10.140.80.210 with HTTP; Fri, 22 Aug 2014 09:59:01 -0700 (PDT) Received: by 10.140.80.210 with HTTP; Fri, 22 Aug 2014 09:59:01 -0700 (PDT) In-Reply-To: References: Date: Fri, 22 Aug 2014 18:59:01 +0200 Message-ID: To: Jan Ehrhardt Cc: PHP Internals Content-Type: multipart/alternative; boundary=047d7bea3b740baad605013ac145 Subject: Re: [PHP-DEV] [RFC] Better type names for int64 RFC From: tyra3l@gmail.com (Ferenc Kovacs) --047d7bea3b740baad605013ac145 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2014.08.22. 17:56 ezt =C3=ADrta ("Jan Ehrhardt" ): > > Andrea Faulds in php.internals (Fri, 22 Aug 2014 16:32:51 +0100): > >I=E2=80=99m very much in favour of this RFC. It is not necessary to chan= ge > >the type names after all; if people turn on compiler warnings, they=E2= =80=99ll > >find out what=E2=80=99s broken anyway. > > 'people'? Which people? > > Will a normal user ever notice anything of the change from long to int? > Isn't this something that only developers of extensions will notice? My > guess is that this chnage is only a minor point when converting > extensions to ng. > People means ext devs here. The concern raised here that if we delay the namechange then early adopters(ext developers adding support for php7) have to update their code twice. I don't think this will major pita (compared to the phpng changes or other upcoming stuff) but would have been nice resolving this before the merge --047d7bea3b740baad605013ac145--