From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.52.186.103 with SMTP id fj7mr8583184vdc.8.1409688647173;
 Tue, 02 Sep 2014 13:10:47 -0700 (PDT)
X-Received: by 10.140.29.5 with SMTP id a5mr53448qga.20.1409688647152; Tue, 02
 Sep 2014 13:10:47 -0700 (PDT)
Path: 
 buffer1.nntp.dca1.giganews.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!m5no5274271qaj.0!news-out.google.com!q8ni8qal.1!nntp.google.com!dc16no638356qab.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Tue, 2 Sep 2014 13:10:47 -0700 (PDT)
In-Reply-To: <c6mii7Fso2rU1@mid.individual.net>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=93.37.251.78;
 posting-account=9fwclgkAAAD6oQ5usUYhee1l39geVY99
NNTP-Posting-Host: 93.37.251.78
References: <f6d1bf8f-cede-435e-9a12-ebae61ea95ca@googlegroups.com>
 <c6juh0F7eb5U1@mid.individual.net>
 <7376f57a-aa89-4ca4-8b44-568dee994707@googlegroups.com>
 <c6mii7Fso2rU1@mid.individual.net>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <79f42f0d-2d15-410c-b3fe-8ab0720b61f9@googlegroups.com>
Subject: Re: Is there a way to do large block of source code comments
From: mockturtle <framefritti@gmail.com>
Injection-Date: Tue, 02 Sep 2014 20:10:47 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Xref: number.nntp.dca.giganews.com comp.lang.ada:188810
Date: 2014-09-02T13:10:47-07:00
List-Id: <comp.lang.ada>

>=20
>=20
> There was also the problem with the interpreted languages like BASIC,
> some of which stored the comments in RAM along with the executable
> program -- if you wrote to many comments, your program no longer fit in
> memory :-(
>=20

Ah, memories... (in this case my own :-)

If I remember correctly, someone used REM lines to store data or little pie=
ces of machine code (often assembled by hand, with the table of the opcodes=
, counting the instructions to determine the width of a relative jump).  Th=
en you run it (with USR?) and since you forgot a POP inside a subroutine th=
e computer would reset...=20