[Coco] Special coding in WAR

[L. Curtis Boyle]

Isn’t there also a bug in Super Extended BASIC where it locks up LIST if it hits an unrecognized token (like say a Disk BASIC command in a program that have loaded onto a cassette based Coco 3)?

Sent from my iPhone

> On Jul 2, 2022, at 5:31 PM, Allen Huffman via Coco <coco at maltedmedia.com> wrote:
> 
> On Jul 2, 2022, at 5:09 PM, robert.gault--- via Coco <coco at maltedmedia.com> wrote:
>> 
>> Allen, An excellent job of determining what is going on in WAR! I'm still not sure why a CoCo2 can LIST those lines while a CoCo3 can't. 
> 
> I’ll have to try that on the CC3 but I bet there’s an extended token in there.
> 
> I am doing a complete write up of this for part 6 of my Attract Screen series at www.subethasoftware.com
> 
>> As to why the lines were used instead of DATA lines that could be POKEd into memory and executed, I guess we will never know. The only reason I can think of is to make it impossible for most users to see how parts of the program worked.
> 
> Was it close to RAM limits for 16K? Otherwise the block character strings could also be generated with CHR$ and DATA.
> 
> 
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>