of course those properties would still have to be declared, and that
can't happen on the fly. However, you're right, in some ways it's better
to have a generic get/set into which you can send both the property and
the value, instead of separate ones for each prop.
--bh
kevin dowd wrote:
>
> Hello,
>
> Is having this kind of set up in your Object O.K.
>
> on settheProp me, theProp, theVal
> me[theProp] = theVal
> end
>
> on broadcastProp me, theProp
> return me[theProp]
> end
>
> settheProp #newProp, 42 -- creates and assigns a new property with the instance
>
> settheProp #existingProp, 42 -- assigns to an existing prop or creats
> a new one if it's not there.
>
> The above means you don't have to write a method (to get/set) a for
> each individual prop in your object. Just a space saver really.
> Obviously you'd do checks on the param variables before you really
> used it.
> --
>
> regards
>
> shoreditch
> london ec2a
>
> [To remove yourself from this list, or to change to digest mode, go to
> http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
> email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
> Lingo-L is for learning and helping with programming Lingo. Thanks!]
--
R. Bhakti Klein
Lingo Programmer, Scientific Learning
http://www.ScientificLearning.com
http://www.BrainConnection.com
**
Baritone, Wicki6
http://www.wicki6.com
***
"On Earth, you can only do little things;
but you can do them with a lot of Love."
-- Mother Theresa
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
