Which is a decent idea, but if you don't have ReflectPermission set in the JVM, you can't do it.
Considering the reflective classes are essentially a form of language extension, you would've thought Sun would've created a Permission object that would allow prevent access to private fields and methods (therefore being useful, and still OO)....
And while I'm whinging, anyone want to tell me what the point of CloneNotSupportedException is? Because I think the clone method is one badly defined method, and one of the problems with Java is if you're going to define a bunch of classes which are going to be used by everyone who uses the language, you should code the classes properly.
a not so interesting wombchimp.
For folks that think they need multiple inheritance, they haven't understood interfaces and inner classes yet.
I'm gonna have to disagree with that bit, but then of course, why else would I reply if I agreed with it all?:)
Yup, you could use interfaces to do multiple inheritance, but in that respect, most classes should have an interface counterpart. The InputStream and OutputStream classes should have been interfaces, but it seems Sun didn't realise providing a simple interface and providing a useful base class was the way forward, and just clumped them together (though they seem to learnt that lesson with the Collection/AbstractCollection classes).
Why can't I define a data store which can be written to and read from in an stream based manner by implementing a couple of interfaces?
Even if they were interfaces, we couldn't take advantage of using the predefined methods in the base stream classes anyway, so this isn't even much of a solution anyway.
Slashdot Mirror
Which is a decent idea, but if you don't have ReflectPermission set in the JVM, you can't do it.
Considering the reflective classes are essentially a form of language extension, you would've thought Sun would've created a Permission object that would allow prevent access to private fields and methods (therefore being useful, and still OO)....
And while I'm whinging, anyone want to tell me what the point of CloneNotSupportedException is? Because I think the clone method is one badly defined method, and one of the problems with Java is if you're going to define a bunch of classes which are going to be used by everyone who uses the language, you should code the classes properly. a not so interesting wombchimp.
I'm gonna have to disagree with that bit, but then of course, why else would I reply if I agreed with it all? :)
Yup, you could use interfaces to do multiple inheritance, but in that respect, most classes should have an interface counterpart. The InputStream and OutputStream classes should have been interfaces, but it seems Sun didn't realise providing a simple interface and providing a useful base class was the way forward, and just clumped them together (though they seem to learnt that lesson with the Collection/AbstractCollection classes).
Why can't I define a data store which can be written to and read from in an stream based manner by implementing a couple of interfaces?
Even if they were interfaces, we couldn't take advantage of using the predefined methods in the base stream classes anyway, so this isn't even much of a solution anyway.
the vaguely interesting wombchimp.