Changes between Initial Version and Version 1 of Ticket #21681, comment 11


Ignore:
Timestamp:
10/12/16 16:11:50 (5 years ago)
Author:
SimonKing
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #21681, comment 11

    initial v1  
    99What about the following scheme:
    1010
    11 - `BaseMetaclass`: Its instances are metaclasses that are basic in the sense that one can combine them.
    12 - `DynamicMetaclass` or `CombinedMetaclass`: Its instances are metaclasses that are dynamically/automatically created from a combination of base metaclasses.
     11- `BaseMetaclass` (instead of `SageMetaclass`): Its instances are metaclasses that are basic in the sense that one can combine them.
     12- `DynamicMetaclass` or `CombinedMetaclass` (instead of `DynamicSageMetaclass`): Its instances are metaclasses that are dynamically/automatically created from a combination of base metaclasses.
    1313- `auto_metaclass`: The function that I currently call `sage_metaclass`. It returns an instance of `BaseMetaclass` or `CombinedMetaclass`, depending on the context.
    1414- The base metaclasses should be named `<Feature>ClassMetaclass`, which corresponds to the existing naming scheme in Sage and means that an instance of `<Feature>ClassMetaclass` is a class that provides a single feature (such as: It has a classcall, or it allows nesting).