Re: Conventions for PETSCII art in assembler files?

From: Ethan Dicks <ethan.dicks_at_gmail.com>
Date: Thu, 12 Nov 2015 17:09:37 -0500
Message-ID: <CAALmimmjc=KmfR7hKXfxed237gTVoYRGTrxYGYTHdjXYnOY2Bw@mail.gmail.com>
On Thu, Nov 12, 2015 at 4:37 PM, Peter Krefting <peter@softwolves.pp.se> wrote:
> In my "bastext" clone of the tok64 utility for converting C64/C128 BASIC
> programs to text (and back), I use this table to represent PETSCII:
>
> http://anonscm.debian.org/cgit/users/peterk/bastext.git/tree/tokens.c#n388

That looks like decimalization of the non-ASCII chars in PETSCII...
that really isn't what I'm after.  I can just put the "art" in the
code as a hex dump (with embedded text strings to be read still
rendered as individual printable chars) for the same effect.

Perhaps I didn't describe clearly enough what I'm after... I'm looking
for examples of any sort of descriptive symbolic labels for the
non-printable PETSCII chars, much like one often saw "{RVS_ON}" and
"{HOME}" in printed listings.

It's unlikly there is "a" standard.  I was just looking for some way
to place these in some assembler so the "art" could be visualized in a
way that a hex dump cannot.  The assembler won't care either way.
It's for the convenience of the humans.

-ethan

       Message was sent through the cbm-hackers mailing list
Received on 2015-11-12 23:00:49

Archive generated by hypermail 2.2.0.