It is possible they were just trying to indent the code to make it look
more like a structured listing to make it easier to find sections.
I was entering lines in AppleSoft from an Open Apple issue. Some lines begin with colons such as:
350 : GOSUB 1000
440 :: GOSUB 1000
I know a colon separates statements on the same line but what are they doing it the above statements? Adding empty statements? For what purpose?
On 2022-08-02 5:15 p.m., Tom Thumb wrote:
I was entering lines in AppleSoft from an Open Apple issue. Some lines
begin with colons such as:
350 : GOSUB 1000
440 :: GOSUB 1000
I know a colon separates statements on the same line but what are they
doing it the above statements? Adding empty statements? For what purpose?
It is possible they were just trying to indent the code to make it look
more like a structured listing to make it easier to find sections.
Jeff Blakeney wrote:I also agree with Jeff and Dave, it's just a programming workaround to provide a little bit of code indenting in a language that doesn't natively support doing that. There would be a slight performance penalty, but probably very little
On 2022-08-02 5:15 p.m., Tom Thumb wrote:
I was entering lines in AppleSoft from an Open Apple issue. Some lines
begin with colons such as:
350 : GOSUB 1000
440 :: GOSUB 1000
I know a colon separates statements on the same line but what are they
doing it the above statements? Adding empty statements? For what purpose?
It is possible they were just trying to indent the code to make it look more like a structured listing to make it easier to find sections.
I agree. This is a technique that I've seen before in Applesoft listings.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 03:36:05 |
Calls: | 6,706 |
Calls today: | 6 |
Files: | 12,235 |
Messages: | 5,350,197 |