Path: csiph.com!weretis.net!feeder8.news.weretis.net!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: D Finnigan Newsgroups: comp.sys.apple2.programmer Subject: Re: Colons in AppleSoft Date: Wed, 3 Aug 2022 20:35:22 -0000 (UTC) Organization: Mac GUI Lines: 17 Message-ID: References: <72291a9a-aeb8-430e-b8e3-abd3f865c750n@googlegroups.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Wed, 3 Aug 2022 20:35:22 -0000 (UTC) Injection-Info: reader01.eternal-september.org; posting-host="25a577b4f32bda6f9df0538728654b3a"; logging-data="2593216"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/BSyQYuXf1KrrfoLP3kCIQ" User-Agent: Mac GUI Usenet Cancel-Lock: sha1:9s0pNvIgP5bWyY7z/EzjonxCsUg= In-Reply-To: Xref: csiph.com comp.sys.apple2.programmer:5983 Jeff Blakeney wrote: > 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.