MV> Captains log, stardate -326477.1:
 MV> Hi Tim, how's life?
TH> Awhile back someone posted a list of all PB reserved keywords, I
  > have unfortunately allowed that list pass out of my system, and I
  > would like to get it posted again.
 MV> You're lucky my HDD is a mess, I haven't deleted it yet:
MV> $ALIAS          $ERROR          $LINK
[...]
MV> XOR
 
Thanks, I guess someone else posted the list, which this time I
grabbed. All I needed to do is fill in a few missing ones (mainly the
*** ones) to complete the list.
In fact I already incorporated this list in the editor I'm working on,
and that part works great. So, again, thanks.
MV> Me too, now I manually type it all uppercased, annoying... Will
  > it contain keyword highlighting too?? Thats not too easy to
  > make...
 
I like the idea of having all reserved words designated by a color
different from the other text. I did this when I developed an
assembler for the Commodire-64 years ago. It was easy to do, but I was
working with three-character memonics. BASIC reserved words vary in
length. That complicates things, and I quickly found that a challenge.
Each word would have to be scanned and checked against the list.
I finished with a function similar to QuickBASIC's 'F2' key. Of
course, I'm using F2 to save files, so it's F4.  Anyway, it lists
all the SUBs and FUNCTIONs. You highlight the one you want to edit and
bam that function is displayed. I think this is a feature of
QuickBASIC I like the most and a must have for me, and probably the
prime motivator for my taking on this project.
I want to decode the help file so I can have implement context
sensitive display on compile errors.
--- Maximus/2 3.01
---------------