When you get tired of LIB cruncher programming, you can find
some relaxation playing my HAPA-MAN. This is my small attempt to
get a feeling of bigger computer's PACMAN on hp48. It is quite
easy to play at 0th level, but reaches maximal difficultness at
level 15 not only because of increased speed, but for the ghosts
get too much intelligent, this is just for information, not to make
you try complete #15. (I did score 7400 with small trick
to send all ghosts home with one vitamine, quickly eat another
vitamine before first one is finished, and wait them in front of
their homes, since for each next ghost before you loose energy
you get 2x more points than before).
Program was written with my "aspera-assembler"(turbo C), on atari
1040 - this Assembler is really dumb, in fact only a hashing
search-and-replace of ascii named commands with appropriate hex,
from times of 28S, based on Mier-Jedrziewitz book.
I didn't put this program on ftps, I only gave it to friends.

There are no bugs, it is well proven,
only ticking clock should be off (it re-activates interrupt, the
program slows on key pressing and can have key buffer filled,
but no memory corruption or losts). Commands are ENTER-up, 7-down,
8-left, 9-right.

[I changed it to the arrow keys - DM]

                 Changing HAPAR is intended for keys and hi-score.
Every key is defined by one byte. This byte is compressed form
of one bit in 13-nibbles something like $0000000100000. One nibble
in that byte represents nibble position(0-12), and second nibble has
one bit set, (value 1, 2, 4 or 8). It is used as a mask for 13-nib
keyboard scannings.

Program is in ONE piece, it fits everywhere, doesn't have strange
parts of code (see source), is not a library (it can be a lib or just
executed from a port).

OK, it has a copyright. You can still give hapaman to your friends.

Have my word that this code WORKS-FINE. It fits its purpose
and is not alike a lot of crap on ftp-s that have many bugs, or
intentional limitations of the usage.

I will be ashamed to put now my name on a program which unneccesary
uses memory or has dirty behaviour, since every author who wrote
something in asm can do that. Even I can do that.

But I did completely the opposite: on many places in mcode there are
safety checks, which can detect internal errors and terminate the
program safetly even its code was damaged by power failure or by other
program :-( (Core-wars have learned me some techinque to make it more
safetly but of course I do not encourage you to poke it randomly and
see how far it can go). Safety checks do not degrade the performance,
neither make code too long (maybe a hunderd bytes).

To run hapaman, put entering game level on stack and issue HAPAMAN.
Valid levels are 0, 3, 6, 9, etc.