Re: Multiple Inheritance / Generated Hidden Code

stephan <[email protected]> Fri, 15 Aug 2025 11:23:12 +0200
Newsgroups	gmane.comp.lang.smalltalk.vwnc
Message-ID	<[email protected]>
This is a multi-part message in MIME format.
--------------opwybfe6WSwmaDwXIKXaSpbz
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 15-08-2025 10:03, andre wrote:
> Thanks, Helge.
>
>> Having said that, none of this hasn't got wide acceptance. Probably 
>> because the problems they were thought to be solving weren't in the 
>> end so ubiquitous that it made sense to pursue them any further.
>
> With most business applications these problems may not arise.
>
> Multiple-inheritance shines with deep UIs (e.g. Dragable, Audible, 
> Exportable, Browseable, Convertible) and complex resource management, 
> where responsibilities and roles are shared  across different class 
> hierarchies.
> With Smalltalk it's easy to build up large convoluted structures, but 
> its hard to properly tear them down and clean up *immediately* (i.e. 
> where GC is not enough). MI helps with encapsulating these 
> responsibilities because the entire life cycle of each 
> role/feature/capability  is coded only in a single place.

An Entity Component System can also be build using just single 
inheritance and composition.

Stephan
--------------opwybfe6WSwmaDwXIKXaSpbz
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 15-08-2025 10:03, andre wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:[email protected]">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div>Thanks, Helge.</div>
      <br>
      <blockquote type="cite"><span
style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 13px;">Having
          said that, none of this hasn't got wide acceptance. Probably
          because the problems they were thought to be solving weren't
          in the end so ubiquitous that it made sense to pursue them any
          further.</span></blockquote>
      <div><br>
      </div>
      <div>With most business applications these problems may not arise.</div>
      <div><br>
      </div>
      <div>Multiple-inheritance shines with deep UIs (e.g. Dragable,
        Audible, Exportable, Browseable, Convertible) and complex
        resource management, where responsibilities and roles are shared
         across different class hierarchies. <br>
      </div>
    </blockquote>
    <blockquote type="cite"
      cite="mid:[email protected]">
      <div>With Smalltalk it's easy to build up large convoluted
        structures, but its hard to properly tear them down and clean up
        *immediately* (i.e. where GC is not enough). MI helps with
        encapsulating these responsibilities because the entire life
        cycle of each role/feature/capability  is coded only in a single
        place.</div>
    </blockquote>
    <br>
    An Entity Component System can also be build using just single
    inheritance and composition. <br>
    <br>
    Stephan<br>
  </body>
</html>

--------------opwybfe6WSwmaDwXIKXaSpbz--