-
1. Re: variable instance getObject versus getValue
dmlloyd Feb 26, 2007 11:42 AM (in response to tom.baeyens)I see. The reason I made them public is that many of them already were... I think there was about four instances of this method that were not public; one of which was on the base class. All the rest were already public. Should I make *all* of the getObject methods be protected?
I had some problem with getValue/setValue in the past, though to be honest I don't remember what it was. I just had this on my todo list to clean up, one way or another. -
2. Re: variable instance getObject versus getValue
tom.baeyens Feb 27, 2007 4:03 AM (in response to tom.baeyens)yes. i think that all the getObject methods on VariableInstance should be protected. if there is a problem with that, let me know.
also, if you bump into the problem again with getValue/setValue, let me know and i can help finding ways in sorting that out. -
3. Re: variable instance getObject versus getValue
dmlloyd Feb 27, 2007 8:42 AM (in response to tom.baeyens)I reverted the change yesterday. I'll do an additional change to update the remaining methods to "protected".