Re: Forbidden variables in BASIC

--===============5796852010413336469==
Content-Type: multipart/alternative; boundary="00000000000032a13d0651e52fee"

--00000000000032a13d0651e52fee
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Remember that my coco script accepts long variable names and makes all of
the characters significant. It will have trouble with these as input, but
it can be set to output them in the tokenized code. It is one of a number
of ways that it can end up making tokenized code that runs fine, but you
may not be able to edit. (it can eliminate otherwise necessary spaces, it
can allow single lines that are of any length that will fit in memory).

On Thu, May 14, 2026 at 6:12=E2=80=AFPM Allen Huffman via Coco <
[email protected]> wrote:

> > On May 14, 2026, at 4:50=E2=80=AFPM, Alex Evans via Coco <
> [email protected]> wrote:
> >
> > The trouble is caused by the tokenizer. If you create an already
> tokenized file by some other means, you can actually use these variable
> names.
>
> Hey, does your CoCo script allow this? I realize it could just build =E2=
=80=9CAS=E2=80=9D
> and other tokens in the .BAS file.
>
> Also, Juan Castro, I think, pointed out you can just use a space:
>
> 10 T O=3D42
> 20 PRINT T O
>
> --
> Coco mailing list
> [email protected]
> http://listserv.adelphi.edu/cgi-bin/mailman/listinfo/coco
>

--00000000000032a13d0651e52fee
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Remember that my coco script accepts long variable names a=
nd makes all of the characters significant. It will have trouble with these=
 as input, but it can be set to output them in the tokenized code. It is on=
e of a number of ways that it can end up making tokenized code that runs fi=
ne, but you may not be able to edit.=C2=A0(it can eliminate otherwise neces=
sary spaces, it can allow single lines that are of any length=C2=A0that wil=
l fit in memory).</div><br><div class=3D"gmail_quote gmail_quote_container"=
><div dir=3D"ltr" class=3D"gmail_attr">On Thu, May 14, 2026 at 6:12=E2=80=
=AFPM Allen Huffman via Coco &lt;<a href=3D"mailto:[email protected]=
u">[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">&gt; On May 14, 2026, at 4:50=E2=80=AFPM, Alex =
Evans via Coco &lt;<a href=3D"mailto:[email protected]" target=3D"_=
blank">[email protected]</a>&gt; wrote:<br>
&gt; <br>
&gt; The trouble is caused by the tokenizer. If you create an already token=
ized file by some other means, you can actually use these variable names.<b=
r>
<br>
Hey, does your CoCo script allow this? I realize it could just build =E2=80=
=9CAS=E2=80=9D and other tokens in the .BAS file.<br>
<br>
Also, Juan Castro, I think, pointed out you can just use a space:<br>
<br>
10 T O=3D42<br>
20 PRINT T O<br>
<br>
-- <br>
Coco mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">Coco@listser=
v.adelphi.edu</a><br>
<a href=3D"http://listserv.adelphi.edu/cgi-bin/mailman/listinfo/coco" rel=
=3D"noreferrer" target=3D"_blank">http://listserv.adelphi.edu/cgi-bin/mailm=
an/listinfo/coco</a><br>
</blockquote></div>

--00000000000032a13d0651e52fee--

--===============5796852010413336469==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Coco mailing list
[email protected]
http://listserv.adelphi.edu/cgi-bin/mailman/listinfo/coco

--===============5796852010413336469==--