×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From: Walden H. Leverich
It's funny, I think the difference is one of grouping too. With the java
approach you're thinking in a ActionObject approach, where the .net
approach thinks in the ObjectAction approach (where action in inferred
from usage).
Eh, I guess I can see that, although really:
myobj.myvar = x;
myobj.setMyVar(x);
Is the grouping really that different? In either case the object is myobj,
and you're executing an action on that object (setting myvar). You could
probably even argue that the Java approach is more strictly OO, because
you're sending the "setMyvar" message to the myobj object. There is no
message/receiver relationship in the .NET syntax, and in fact it looks as
though the property itself is the receiver, which isn't true - it really is
the object receiving and acting upon the message.
But now we're truly drifting off into the chasms of ultra-nerddom. In fact,
I have a sudden urge to break my glasses and tape them...
Joe
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
