switch case and default must not have semicolons

[kenguest]

Update section 5.2 advising that semi-colons must not be used in switch statement.

Resolves #128

[theodorejb]

I don't think this is needed, since the example already uses colons, and the semicolon syntax is now deprecated in PHP itself.

[kenguest]

For some people, implicit/implied requirements as shown in sample code is not as clear-cut compared to when outlined in the prose of the requirements document, so this is still very much needed.

[kenguest]

I've changed the wording to below:

The caseanddefault keywords MUST use colons as shown in the sample code below.

[theodorejb]

The description should probably mention that this will close #128.

[kenguest]

The description should probably mention that this will close #128.

I've updated the description accordingly.

[lpd-au]

Suggested change

[Crell]

(Adjusted reference in the summary to match GitHub automation expectations.)

[Crell]

@jrfnl Would this language be good enough for you? It's a bit wiggly in how it specifies things, but maybe that's OK in this case?

[jrfnl]

Suggested change

	The `case` and `default` keywords MUST use colons as shown in the sample code below.
	The `case` and `default` keywords MUST use colons.

[theodorejb]

I'd prefer the existing language, so that it also applies to formatting of the colons (e.g. there shouldn't be whitespace between case and :).

[jrfnl]

@jrfnl Would this language be good enough for you? It's a bit wiggly in how it specifies things, but maybe that's OK in this case?

I still think it's kind of redundant, but if this is being made explicit, than the text should be leading. The reference to the sample code like this, would be the only one of its kind in the whole document, so to me, it feels like it doesn't belong.

If anything, the rule as described now, still leaves room for code like this - take note of the redundant curly braces -, which IIRC is discouraged:

switch ($foo) {
    case 10 : {
        // Do something.
        break;
    }
}

I wonder if PERCS should be explicit with an opinion about redundant curlies in this context if the use of the colon is being made explicit now anyway ?

[Crell]

(With editor hat on) I'm open to not doing anything here if that ends up being the consensus. Or if the consensus is we should specify something, that's OK too. I don't have a large personal stake here.

I... didn't know extra braces were legal, either. 😅 I'd be OK with forbidding those if the rest of the WG is.