Jump to page: 1 2
Thread overview
Semicolon?
Mar 31, 2021
Arun
Mar 31, 2021
deadalnix
Apr 01, 2021
Walter Bright
Apr 01, 2021
Walter Bright
Apr 01, 2021
jmh530
Apr 01, 2021
evilrat
Apr 01, 2021
evilrat
May 13, 2021
rempas
Apr 02, 2021
Kagamin
Apr 03, 2021
John Colvin
May 11, 2021
Witold Baryluk
May 11, 2021
deadalnix
May 11, 2021
evilrat
May 11, 2021
Witold Baryluk
March 31, 2021
Just curious. Does the compiler need semicolon anymore? Are there corner cases that don't work without semicolon?
March 31, 2021
On Wednesday, 31 March 2021 at 21:51:07 UTC, Arun wrote:
> Just curious. Does the compiler need semicolon anymore? Are there corner cases that don't work without semicolon?

They aren't strictly needed most of the time, but they do make things much clearer, especially when you have a syntax error.
March 31, 2021
On 3/31/2021 2:59 PM, deadalnix wrote:
> On Wednesday, 31 March 2021 at 21:51:07 UTC, Arun wrote:
>> Just curious. Does the compiler need semicolon anymore? Are there corner cases that don't work without semicolon?
> 
> They aren't strictly needed most of the time, but they do make things much clearer, especially when you have a syntax error.

Yup. They're a form of redundancy like a parity bit is.
March 31, 2021
On 3/31/21 10:13 PM, Walter Bright wrote:
> On 3/31/2021 2:59 PM, deadalnix wrote:
>> On Wednesday, 31 March 2021 at 21:51:07 UTC, Arun wrote:
>>> Just curious. Does the compiler need semicolon anymore? Are there corner cases that don't work without semicolon?
>>
>> They aren't strictly needed most of the time, but they do make things much clearer, especially when you have a syntax error.
> 
> Yup. They're a form of redundancy like a parity bit is.

There are a few cases that would be ambiguous. Not sure how realistic:

auto a = b;
*c;

Without semicolons the semantics would be different.
April 01, 2021
On 3/31/2021 7:40 PM, Andrei Alexandrescu wrote:
> There are a few cases that would be ambiguous. Not sure how realistic:
> 
> auto a = b;
> *c;
> 
> Without semicolons the semantics would be different.

D disallows pointless expressions like *c; so it would parse as b*c. Not really helpful in diagnosing the problem.

It's one of those perennial good ideas, like implicit declarations, that resurface every couple of years. It isn't obvious why they are a bad idea, until you work with them for a while.
April 01, 2021
On 3/31/21 10:40 PM, Andrei Alexandrescu wrote:
> On 3/31/21 10:13 PM, Walter Bright wrote:
>> On 3/31/2021 2:59 PM, deadalnix wrote:
>>> On Wednesday, 31 March 2021 at 21:51:07 UTC, Arun wrote:
>>>> Just curious. Does the compiler need semicolon anymore? Are there corner cases that don't work without semicolon?
>>>
>>> They aren't strictly needed most of the time, but they do make things much clearer, especially when you have a syntax error.
>>
>> Yup. They're a form of redundancy like a parity bit is.
> 
> There are a few cases that would be ambiguous. Not sure how realistic:
> 
> auto a = b;
> *c;
> 
> Without semicolons the semantics would be different.

Languages without semicolons generally use some other delimiter, usually newline.

The nice thing about semicolons is that you can pick whatever format you want, so whitespace can be done however you want. But it's a curse as well.

I've been recently teaching a class with D to homeschool kids with super-limited coding experience (in fact, everything they know they learned from me pretty much). We started with Javascript (optional semicolons), and lua ("begin/end" tags), and now on D, I find one of the most common errors that they have a hard time solving is a lack of semicolon. I don't know if this is specific to D, but I do notice that forgetting punctuation usually produces a wall of errors, of which only the first one is relevant (usually). When you have not been programmed to write punctuation in coding properly, the oddest things come out. I sometimes spend minutes trying to figure out why their code is not compiling, when I finally notice a stray closing curly brace somewhere off in the distance.

Not sure if there's a way to improve it.

-Steve
April 01, 2021
On Thursday, 1 April 2021 at 16:02:48 UTC, Steven Schveighoffer wrote:
> [snip]
>
> I don't know if this is specific to D, but I do notice that forgetting punctuation usually produces a wall of errors, of which only the first one is relevant (usually). When you have not been programmed to write punctuation in coding properly, the oddest things come out. I sometimes spend minutes trying to figure out why their code is not compiling, when I finally notice a stray closing curly brace somewhere off in the distance.
>
> Not sure if there's a way to improve it.
>
> -Steve

Yeah that's an annoying thing to catch. Reminds me of the video with the basketball players passing the ball as the guy in the gorilla suit walks through, the semicolon is just not the thing you're focusing on sometimes.

The only thing I can think of is that when the compiler sees an error, it can check if the prior line ends with a semicolon, then it can check if the error would be generated if a semicolon is added. Finally, display an error about missing a semicolon.
April 01, 2021

On Thursday, 1 April 2021 at 17:10:02 UTC, jmh530 wrote:

>

The only thing I can think of is that when the compiler sees an error, it can check if the prior line ends with a semicolon, then it can check if the error would be generated if a semicolon is added. Finally, display an error about missing a semicolon.

I think in languages where it is optional the rules are a bit different.

e.g. the only thing that can force a newline NOT to be treated as semicolon is AFTER following symbols:

* / - + : ! @ . , ( { [

They are like normal punctuation in a real sentence, if you put it you are going to end a sentence, which is natural, otherwise it is abrupt and doesn't makes sense.

So a junk like

int a = b
*c

in no way is equal to

int a = b * c

April 01, 2021

On Thursday, 1 April 2021 at 19:32:17 UTC, evilrat wrote:

>

e.g. the only thing that can force a newline NOT to be treated as semicolon is AFTER following symbols:

* / - + : ! @ . , ( { [

Ok, turns out life is a bit more complex than that and we have things like strings and functional paradigm.

So in addition to the rule above it seems we might need overlapping rule BEFORE for symbols like . and (

April 02, 2021
On Wednesday, 31 March 2021 at 21:51:07 UTC, Arun wrote:
> Just curious. Does the compiler need semicolon anymore? Are there corner cases that don't work without semicolon?

See http://delight.sourceforge.net/
« First   ‹ Prev
1 2