XPost: alt.os.development   
   From: maxim@storagecraft.com   
      
   > 1. There are technical and theoretical problems with OO languages. Many   
   > things (multiple dispatch, multiple inheritance, ad-hoc supertypes,   
   > extensible active objects (tasks), extensible protected objects) are quite   
   > difficult. Basically nobody knows how to do them right. And this is just on   
   > the language level.   
      
   Yes, and now note - language is a _tool_, it has no value by itself, its value   
   is only in the tasks it can solve.   
      
   So, if you're getting lost if the internals of the _tool_ - this is very bad.   
   Maybe use simpler tools? or the simpler features of this complex tool? maybe   
   such complex features serve no purpose then self-satisfaction of their author?   
      
   For instance, most discussions I've heard from .NET/C# developers are the   
   "smart new features" of the language, and IDE settings. Sorry, but how this   
   relates to the development itself?   
      
   Looks like these people are spending lots of time trying to govern and   
   comprehend their tools. Then they get accustomed to extremely complex ways of   
   solving the problems, and start to consider this - normal.   
      
   The "use the newest and smartest possible new features of the new tool"   
   paradigm is evil for me. It increases the number of issues and not decreases   
   it.   
      
   > 2. Even if there were a good OO language supporting advanced ADTs, OS   
   >would   
   > require something more. Present types systems are co-operative. You can   
   > call a private method even if you no right to do it. For an OO OS one would   
   > need a memory access based protection of dispatching tables and private   
   > members. That is another problem to solve.   
      
   That's why there is no widely-used OO OSes in the world :-). Anyway the   
   C++-style private-public division is evil. It mandates that all private stuff   
   is declared in the same header as the public part of the class, thus exposing   
   the internal details and introducing major build dependencies (add a private   
   field to some base class and get the full rebuild).   
      
   Also note: OO OS will be 100% tied to the particular OO language.   
      
   --   
   Maxim Shatskih, Windows DDK MVP   
   StorageCraft Corporation   
   maxim@storagecraft.com   
   http://www.storagecraft.com   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)