"Steven Nagy" <le*********@hotmail.comwrote in message
news:11**********************@b28g2000cwb.googlegr oups.com...
That seems to be a bit like saying "Lets remove the while loop because
someone could do a while(true) {}
While I appreciate that it wasn't actually your answer,
In this case the result is not a gpf.
I have to
believe that it should be up to the programmer to make those mistakes,
learn from them, and in turn become better at it, rather than just
restricting access to the inheritance of the class. Microsoft shouldn't
make my programming choices for me...
One of the criterias for a component for .net appears to be that it should
be impossible to make it gpf (or at least difficult). This might not have
been possible if inheriting the bitmap class or might have been difficult.
On one hand I do agree that it's good to be able to do what you want it
would also be a pain to have a gpf on the odd occassion when an app was
released. That would be a complete bugger to find so I'd probably prefer to
have the non-inheritable bitmap.
That being said, I'd prefer to have a stable, inheritable bitmap :-)
Michael