Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98692
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1490897949.13915.56.camel@schlueters.de>
References: <CAEJj8DkrQGLLF+H4EwZYQadftN+4=Oxz7kHEz_j1SrTKSDkAZg@mail.gmail.com>
 <CANaX5nezxEqRg75unoVnUko5xPB00Q9dpeM+nrtCkCatdUS=FA@mail.gmail.com> <1490897949.13915.56.camel@schlueters.de>
Date: Thu, 30 Mar 2017 12:25:51 -0600
Message-ID: <CAObuZdtPV56oVzZ-xuZX1XKwVNwLDz-1OiTK3WBbDZhrzP7+fw@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: Davey Shafik <davey@php.net>, dmitr y <d726627@gmail.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c18fceca2b4ba054bf6d201
Subject: Re: [PHP-DEV] ; on the end of the line
From: derokorian@gmail.com (Ryan Pallas)

--94eb2c18fceca2b4ba054bf6d201
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 30, 2017 at 12:19 PM, Johannes Schl=C3=BCter <johannes@schluete=
rs.de>
wrote:

> On Do, 2017-03-30 at 00:07 -0700, Davey Shafik wrote:
> > Notice each of these has two statements. (Note: I don't think any of
> > these
> > are particularly good ways to write readable code, but they are all
> > syntactically valid code).
>
> The imo more relevant cases are the one where an optional semicolon
> causes unclear behavior. Consider we make it optional, what is the
> behavior of this code:
>
> <?php
> $a =3D [1, 2, 3]
> [rand(0, 2)]
> var_dump($a)
> ?>
>
> $a could either be an array with three elements or a single integer
> value which is randomly chosen out of the array. Requiring a statement
> separator like semicolon makes this clear.
>
> > While I know some languages make semicolons optional (javascript), or
> > omit them entirely (python),  semicolons in PHP will not be going
> > away (or optional) any time soon.
>
> JavaScript shouldn't be our role model here - it has relatively complex
> rules for this (essentially "if treating a following line as belonging
> to the statement leaves valid code then treat it as part of the same
> statement else terminate the statement on the new line")
> Python does this by requiring indention on the continuing line. As PHP
> isn't whitespace-programming this isn't applicable for s either, while
> it's a way more consistent design than JavaScript in that regard.
>

I would also point out, that I haven't worked on a JavaScript project in
ages where the conventions / rules of that project allow leaving off
semi-colons. While the language may make it acceptable, most organizations
have rules requiring semi-colons. The reason is to avoid the disambiguation
as Johannes has pointed out.


>
> johannes
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--94eb2c18fceca2b4ba054bf6d201--