on 3/10/06 6:49 PM, Thomas Tempelmann at [EMAIL PROTECTED] wrote: > I just found something I did not expect to work like this: > > dim d1, d2 as new Date > > I did expect that this would create TWO new Date instances, one for > d1, and one for d2. > > Instead, there's only one instance which gets assigned to both d1 and d2. > > You do not need to explain to me why it happens like this - I ask the > others of you if you agree that this is a GOOD result that you all > want. > > Because I'd rather ask that the compiler gives an error to avoid this > rather ambiguous effect: I say that if someone wants to have d1 and d2 > assigned the same value here, he should rather write this explicitly > to avoid this possible confusion.
I agree that the compiler should generate an error if there is more than one variable defined and new is used. I have never liked this syntax. Chris _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
