I should have been clearer: there's a good chance you won't need to
use a class interface. But, for example, if you have low-level
generic code, which sometimes you're using inside the container
control, and sometimes outside, it will greatly simplify your code to
use a class interface. So I just wanted to point out the possibility.
I agree with Guyren here. Implementing an interface could hide some
of the implementation details and make the getter and setter method
calls more flexible.
But then, what do I know? It's 1:00 AM, I have to be up at 6:00 AM
to sit through 10 hours of pharmacology lectures with a sprained
back, and a migraine just hit. (Can anything else go wrong?)
-Scott.
Dr. Scott Steinman
Brought to you by a grant from the Steinman Foundation (Thanks, Mom
and Dad!)
Recommended by Major University Studies Over the Leading Brand
steinman at midsouth dot rr dot com
I hope I die peacefully in my sleep like my grandfather. . .not
screaming in terror like his passengers. -- "Deep Thoughts", Jack Handy
_______________________________________________
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>
