3 Replies Latest reply on Feb 27, 2007 8:42 AM by dmlloyd

    variable instance getObject versus getValue

    tom.baeyens

      David,

      the idea is that getObject is an internal method and that getValue is used by clients.

      sorry for not documenting this properly.

      can you revert those changes and use getValue instead ?

      or was there some other reason why you made the getObject public ?

      regards, tom.

        • 1. Re: variable instance getObject versus getValue
          dmlloyd

          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

            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

              I reverted the change yesterday. I'll do an additional change to update the remaining methods to "protected".