NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
jk2addict (4946)
jk2addict
(email not shown publicly)
http://today.icantfocus.com/blog/
AOL IM: chrislaco (Add Buddy, Send Message)
Yahoo! ID: chrislaco@sbcglobal.net (Add User, Send Message)
Jabber: laco@scribblewerks.com
(email not shown publicly)
http://today.icantfocus.com/blog/
AOL IM: chrislaco (Add Buddy, Send Message)
Yahoo! ID: chrislaco@sbcglobal.net (Add User, Send Message)
Jabber: laco@scribblewerks.com
Friday August 29, 2008
12:56 PM
Why the Overridable hate in .NET?
One of the things that I curse about on a weekly basis when using
That seems silly to me coming from the land of Perl. The author of the original class has presumed to know which methods/props I might like/have to subclass and which ones I won't. Good old Perl. I can override anything I want and it stays out of my way.
Then of course, there are Sealed classes which can't even be inherited. I can't even create my own custom DateTime class. At least now that 3.0 has Extensions, I can add my methods to the DateTime object.
an endless discussion thread about what features to include.
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Why the Overridable hate in .NET? 0 Comments More | Login | Reply /