Ro> I find it *useful* but *annoying*. I much prefer lowercase.

  It must be just me. In Pascal, I start off writing things like
SmallIntenger... and then I don't like the look of the l's and switch
to lower case the next time. I seem to run specials, so it's just as 
well for VB to put it in upper case and have done with it. In fact, 
I rather like the way that Delphi does in in bold.

 Ro> The automatic formatting is nice, though. (eg: "PRINT A%"
 Ro> becomes "PRINT A%"). It was a bit of a surprise when I was
 Ro> trying out the PowerBASIC demo: it doesn't fiddle with
 Ro> capitalisation or spacing at all. 

  I like that too...

 Ro> I wrote a little util a while ago which extracts all the
 Ro> elements of your source code: all keywords, variable names,
 Ro> etc, and lists them once only (regardless of how many times
 Ro> they appear in the source).

  What a good idea!

 Ro> Then by sorting that list you can see immediately when you have
 Ro> mis-spelt variable names. The problem with QB is that it's not
 Ro> fussy: if you use Hello% somewhere and then Helo% somewhere
 Ro> else, it will assume they are two quite different variables and
 Ro> not complain. VB has an "OPTION EXPLICIT" which forces you to
 Ro> declare all variables a la C/Pascal, which solves this problem.

  Yes. I never use it any other way. I am the master of the misspelled
variable. Without declarations, I end up with lots more than I expect.

 Ro> BTW, if you have VB/DOS standard, try this trick (no guarantees, back
 Ro> up first) 
 Ro> -------------------------------
 Ro> At offset 00000210h, STD has 9FF3h, PRO has CD05h   [BC.EXE]

 Ro> Similarly, the VBDOS.EXE IDE is the same length for both
 Ro> versions, and has exactly the same byte difference, this time at
 Ro> offset 00006B10h.
 Ro> -------------------------------

  Aaarrgh! I've got the PRO version of VB/DOS. Robbed again. I *hate*
Mickey!

Regards,
Bob
___ Blue Wave/QWK v2.12
@EOT:

---