Hi again Jamshid!
JK>SL>and then in the function definitions ...
JK>I've had that happen to me more than once....  ;)
Oh well.  I've learned something from it, and there's something to be
said for every lesson, however learned. :)
JK>SL>What precisely does the LOCAL keyword do in a function definition?
JK>LOCAL is the default.  It means that all variables in the following
JK>SUB/FUNCTION are local to it.  You don't have to state that explicitly,
JK>because it is the default.  Had that been SHARED, all variables would be
I understand.  On your recommendation some months ago, I did purchase a
copy of Steve McConnell's book "Code Complete".  I've been going through
it, a little at a time, and trying to put some of the things I've
learned there into practice.  I struggled through some of the
concepts re. information hiding, etc., but I've learned a lot.  It's
been a good exercise, and I think I've really improved some of my code as
a result.  Anyway, I've finally gotten the nerve to try some of the
other things you suggested re. declaring everything and giving the
compiler an opportunity to catch "spelling problems", and I think there's
been some benefit there too.
That said, I've gotten used to the idea of trying to make sure
anyone else who might look at what I've done can understand what I
was up to.  To this end, declaring even the default type/scope seems to
enhance readability for anyone who understands what it will do.
JK>SL>And on a slightly different PowerBASIC topic ...
JK>SL>What does PowerBASIC do with constants when they're declared?  I know
JK>SL>that it's possible, though undesirable, to have two *variables* of two
JK>SL>different types called (for example) Nuts$ and Nuts#.  This seems to be
JK>SL>impossible if you've turned on the full variable checking, because you
JK>SL>can't declare them this way.  Please correct me if I'm wrong.
JK>You cannot, with declaration mode on, have two variables WITHIN THE SAME
JK>SCOPE with the same base name.  This is how C programmers have always
JK>had it.  I prefer DIM a AS STRING and SUB MySub (A AS INTEGER, etc.)
Me too now!  When I'm doing this I can usually find room to fit a
concise description of the variable's use within 80 characters.
JK>The old-style suffixes are very nasty to parse with preprocessors.  You
What does a preprocessor do, and why might you use one?
JK>SL>Now, as I understand it, PowerBASIC declares named constants by
JK>SL>preceding the "variable name" with the type, something called an
JK>SL>"equate."  If I declared a constant called %TRUE, which I obviously 
might
JK>SL>use as the integer representation of a boolean flag, must I also
JK>SL>use %TRUE throughout the body of the program when evaluating some
JK>SL>expression relationship to %TRUE, or can just TRUE be made to suffice?
JK>Constants are preceded by %, not the type, and may only be numeric.  I'd
JK>like to see string constants.  TRUE and %TRUE are not one and the same.
JK>%TRUE is a global constant, whereas TRUE is an identifier that may be of
Ahh!  That's the distinction.  I've been working with Scriptmaker
lately, a BASIC implementation for Windows that comes with Norton
Desktop for Windows.  It uses the Microsoft CONST declaration for all its
constants, and a constant takes the type of its first assigned value.  I
think I like that better.
JK>any datatype.  The %nnnnn format makes it quite clear upon seeing it
JK>in the code that its value is numeric, integer, and cannot be
JK>changed.  TRUE can be changed, but to what, we don't know.
This "recognition" is the purpose for some of the variable naming
conventions (notably Hungarian) as well isn't it?
Thanks for your comments Jamshid!  A little inspiration goes a long
way.  All the best.
-=        Steve Legg        -=-      RelayNet ->CRS     =-
-=  Oshawa, Ontario CANADA  -=-  steve.legg@canrem.com  =-
---
 * OLXWin 1.00a * Programmers don't get sniffles, they get a CODE.
--- QScan/PCB v1.17b / 01-0348
---------------