In version 2, you are restricting yourself to using the method within
the object. In fact, I don't see any reason to have the pCurrent
parameters. They're accessible within your object, if I understand
yourself. You could just refer to them without having them as
parameters, or needing to pass
Good answer. Thanks, Kerry.
- Michael M.
In version 2, you are restricting yourself to using the method within
the object. In fact, I don't see any reason to have the pCurrent
parameters. They're accessible within your object, if I understand
yourself. You could just refer to them without
I just tried it, and I found that version #2 does not compile. I get
a comma expected within the pCurrent.pModule part of the on
mHandler line.
If I think back real hard to my days of writing compilers, I can
understand why this would be. Parameters that are declared on a
handler line are
On Mar 23, 2004, at 9:44 AM, Kerry Thompson wrote:
In version 2, you are restricting yourself to using the method within
the object. In fact, I don't see any reason to have the pCurrent
parameters. They're accessible within your object, if I understand
yourself. You could just refer to them
Hope that made sense ... and I hope it is right :)
Makes a lot of sense, Irv. It's a great explanation and it certainly
sounds right. Thanks very much for your insight.
- Michael M.
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi
Irv,
You are right - parameters are stack allocations; I've never seen anyone
directly have a property as a parameter and pick them up directly. I
suppose you could write a compiler to do so - but C and Lingo aren't
written that way, afaik. If it does work in Lingo then someone went out of
