A:=B:=C:=D:=0;
With the continuator idea this coding would look as follows:
Good single line code:
A:=B:=C:=D:=0
Bad multi line code:
A:=
B:=
C:=
D:=
0
^This would not be allowed and lead to error messages.
Good multi line code:
A:=;
B:=;
C:=;
D:=;
0
^ This would lead to a good compile.
In article <85795$54978fe1$5419aafe$2...@news.ziggo.nl>, skybuck2000
@hotmail.com says...
>
> Hello,
>
> In the past I wrote about pascal's ; mistake.
>
> ; should be used as a continuator.
>
> I just made a programming mistake which solidifies/merits my idea:
>
> The programming mistake was t
On Mon, Dec 22, 2014 at 2:53 PM, Steven D'Aprano wrote:
> On Mon, 22 Dec 2014 04:28:33 +0100, Skybuck Flying wrote:
>
>> I don't like inconsistencies, it's frikking annoying.).
>
> I don't like cross-posting trolls, they're frikking annoying.
My first thought was that it had been sent to the wron
On Mon, 22 Dec 2014 04:28:33 +0100, Skybuck Flying wrote:
> I don't like inconsistencies, it's frikking annoying.).
I don't like cross-posting trolls, they're frikking annoying.
> Bye,
Oh, if only that were true.
--
Steven
--
https://mail.python.org/mailman/listinfo/python-list
Hello,
In the past I wrote about pascal's ; mistake.
; should be used as a continuator.
I just made a programming mistake which solidifies/merits my idea:
The programming mistake was this:
vBattlefieldLosingWarrior :=
// modified warrior and brain
vSimulatorWinningWarrior := vBattlefieldBatt
