On Monday, 19 September 2016 at 20:42:22 UTC, jmh530 wrote:
> I don't see a reason to make that sort of change within the D language or DMD, especially when something like Delight exists and probably accomplishes exactly what the OP had wanted.
>

Delight is not what i meant, i meant something like this:

module test
import std.stdio

void main() {
    write("Hello");
    writeln("world")
}

On Tuesday, 20 September 2016 at 11:24:29 UTC, eugene wrote:
> On Monday, 19 September 2016 at 20:42:22 UTC, jmh530 wrote:
>> I don't see a reason to make that sort of change within the D language or DMD, especially when something like Delight exists and probably accomplishes exactly what the OP had wanted.
>>
>
> Delight is not what i meant, i meant something like this:
>
> module test
> import std.stdio
>
> void main() {
>     write("Hello");
>     writeln("world")
> }

Without the semicolons, I have to parse the code myself, which makes it harder to read. Do that with 1000 lines of code and it gives me a headache. I have written many tens of thousands of lines of R code and hate the lack of semicolons. This is purely a matter of preference.

On Tuesday, 20 September 2016 at 12:00:00 UTC, bachmeier wrote:
> Without the semicolons, I have to parse the code myself

could you, please, explain, why do you parse code yourself?

On 09/20/2016 08:20 AM, eugene wrote:
> On Tuesday, 20 September 2016 at 12:00:00 UTC, bachmeier wrote:
>> Without the semicolons, I have to parse the code myself
>
> could you, please, explain, why do you parse code yourself?

That's what happens in the brain when you read code. He's not talking about actual LR/LL/etc parsing here, but the mental equivalent. Just like you parse a sentence when you read it by noticing the spaces defining where words are. And the commas separating sections of a sentence, and periods/capitalization separating the sentences, in-sentence capitalization signaling proper nouns, etc. All of those are *technically* unnecessary too, but notice how much harder it is to read (ie, "parse") when they're absent.

thats what happens in the brain when you read code hes not talking about actual lr ll etc parsing here but the mental equivalent just like you parse a sentence when you read it by noticing the spaces defining where words are and the commas separating sections of a sentence and periods capitalization separating the sentences in sentence capitalization signaling proper nouns etc all of those are technically unnecessary too but notice how much harder it is to read ie parse when theyre absent

On Tuesday, 20 September 2016 at 14:19:50 UTC, Nick Sabalausky wrote:
> Just like you parse a sentence when you read it by noticing the spaces defining where words are. And the commas separating sections of a sentence, and periods/capitalization separating the sentences, in-sentence capitalization signaling proper nouns, etc. All of those are *technically* unnecessary too, but notice how much harder it is to read (ie, "parse") when they're absent.
>

one doesn't parse a sentence when one reads it, one translates a sentence into images; why do you compare native speech sentences with a programming language statements?

one doesn't parse a sentence when one reads it
one translates a sentence into images
why do you compare native speech sentences with a programming language statements

On Tuesday, 20 September 2016 at 15:07:31 UTC, eugene wrote:
>
> one doesn't parse a sentence when one reads it, one translates a sentence into images; why do you compare native speech sentences with a programming language statements?
>
> one doesn't parse a sentence when one reads it
> one translates a sentence into images
> why do you compare native speech sentences with a programming language statements

Yes and no. Of course it's like an image (i.e. you see it), but commas, colons, fullstops etc. _help_ you to find your way around in the text and sometimes even help to disambiguate. You'll notice this in the comment section under newspaper articles: sometimes it's hard to understand a sentence at first reading, when people leave out commas where they would make sense. So you have to re-analyze the sentence. E.g.:

"I was talking to Joan and Peter went to the shop to buy some sweets."
vs.
"I was talking to Joan, and Peter went to the shop to buy some sweets."

I'm sure someone can find an example where a sentence would be ambiguous without proper punctuation.

Anyway, why don't you grab the compiler and make a version that accepts line breaks and ";" - and see what happens?

On Tuesday, 20 September 2016 at 15:28:51 UTC, Chris wrote:
> Anyway, why don't you grab the compiler and make a version that accepts line breaks and ";" - and see what happens?

yes, i've written about it in the thread before

On Tuesday, 20 September 2016 at 15:31:21 UTC, eugene wrote:
> On Tuesday, 20 September 2016 at 15:28:51 UTC, Chris wrote:
>> Anyway, why don't you grab the compiler and make a version that accepts line breaks and ";" - and see what happens?
>
> yes, i've written about it in the thread before

Then try to compile Phobos and a variety of D projects on Github and publish the results. It'd be interesting to see what problems you encounter. Then you might write a tool like dfix that fixes the source code so that ";"-less code is parsed properly etc. But is it really worth it?

On Tuesday, 20 September 2016 at 15:36:42 UTC, Chris wrote:
> On Tuesday, 20 September 2016 at 15:31:21 UTC, eugene wrote:
>> On Tuesday, 20 September 2016 at 15:28:51 UTC, Chris wrote:
>>> Anyway, why don't you grab the compiler and make a version that accepts line breaks and ";" - and see what happens?
>>
>> yes, i've written about it in the thread before
>
> Then try to compile Phobos and a variety of D projects on Github and publish the results. It'd be interesting to see what problems you encounter. Then you might write a tool like dfix that fixes the source code so that ";"-less code is parsed properly etc. But is it really worth it?

It'd be interesting, because it would finally provide data for the ever-recurring question of whether to have semicolons or not.

¿How would you handle cases like

debug { writeln("Error"); return; }

of just

debug { writeln("Error"); }

On Tuesday, 20 September 2016 at 15:36:42 UTC, Chris wrote:
> But is it really worth it?

this was my question at the beginning of the thread