首页> 外文会议>ECOOP'92, European conference on object-oriented programming >Import is Not Inheritance Why We Need Both: Modules and Classes
【24h】

Import is Not Inheritance Why We Need Both: Modules and Classes

机译:导入不是继承为什么我们都需要:模块和类

获取原文
获取原文并翻译 | 示例

摘要

The design of many popular object-oriented languages like Smalltalk, Eiffel, or Sather follows a certain trend: The class is the only structuring form. In this paper, the need for having modules besides classes is claimed. Modules stem from a different language family and at first glance it seems that they can easily be unified with classes. Among other things, unifying modules and classes carries the danger of unifying the import and inheritance relationships. Constructs in several languages arc discussed that indicate that modules and classes should indeed be kept separate.
机译:许多流行的面向对象的语言(例如Smalltalk,Eiffel或Sather)的设计都遵循一定的趋势:类是唯一的结构形式。在本文中,要求除类之外还具有模块。模块源自不同的语言家族,乍一看似乎可以轻松地将它们与类统一。除其他事项外,统一模块和类具有统一导入和继承关系的危险。讨论了几种语言的构造,这些构造指示确实应该将模块和类分开。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号