There was this:
Speaking of mis-used commands and side-stepping some of the given code
craziness...
It is better practice to atomize the code into discrete elements such
as...
Var1.F = oconv(Var1, 'MD0')
Var2.F = oconv(Var2, 'MD2')
Var3.F = oconv(Var3, 'MD4')
Thanks David. I feel less alone.
As far as the order of processing, it's an acquired taste. We all recall
learning the order of calculations between +, -, / and *. Despite it
compiling without parenthesis and coming up with the right answer, I too
like to make it more obvious with using parens.
That's what the compiler is for. After all, it has the final word on the
sourse code and any 'pre-compilers'.
I'm having a similar dialog with someone on the D3 forum about their
insistence upon 'changing' the syntax of data/basic statements as he feels
that their syntax is not 'natural'. So he
Mark:
I always thought a principle of languages was to separate words. In this
sentence,
... programs ago that PRINT X/100R2,#10 ...
you've separated each word, within the sentence, with a space, but not the BASIC
code. Why not BASIC?
PRINT (X/100) R2,(#10)
or
X = (4 + 5) * 7
I
