Le 11 avr. 07 à 00:58 Matin, [EMAIL PROTECTED] a écrit: > On Apr 10, 2007, at 22:52 UTC, Arnaud Nicolet wrote: > >> That's really strange. I remember having ran in this issue as well as >> a discussion about that in this mailing list. >> >> Now, it seems everyone answers the opposite (maybe my problem also >> disappeared magically). > > I think you're confusing it with a different effect. If you have > > A = B > > so that A and B refer to the same Date object (and there are less > obvious ways to do this, with multiple declarations in one Dim > statement), and then you *modify* (not reassign!) one of the objects, > like so: > > A.TotalSeconds = 42 > > then of course this modifies the object referred to by B as well, > since > A and B both refer to the same object. > > But an assignment is different -- that doesn't modify an object; it > makes a variable refer to some other object.
Yes, that makes sense, thanks. I think I don't remember the issue I had correctly (I thought it was not what you're saying, but that would be nonsense). I apologize for my wrong answer. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
