[sv-ec] Questions on Arturo's class scheduling/extension approach

Arturo,

In terms of your basic idea for using parameterization
in conjunction with classes, I would like to specifically
list some of the questions that I raised during the
face-to-face.  I think that we need to have some direct
comparison of the nature of the rules that result from
our suggestion versus your suggestion and your desire to
have stronger enforcement of program versus design.

Specifically:
   1) is there any correspondence to our "schedulefree" class?
   2) under what conditions (if any) is one required to
      use the parametric form?  When (if ever) would it
      be an error?
   3) what restrictions (if any) exist in terms of extension
      prior to and/or after defining the parametric binding?
      Some simple rules (similar to the three we proposed)
      would be useful.
   4) What is the relationship between predefined class
      types such as mailbox (C.2) and a context parametric
      class?
   5) Are there any restrictions regarding containment
      relationships?  How are those restrictions expressed?
   6) It seems that any reusable class would have to be
      defined in a parametric manner.  Since, I believe,
      parametric types become instantiated types when
      passed through a type parameter, is there any
      mechanism for having something equivalent to a
      schedulefree class propagate through a module
      hierarchy?

Once we see more details we can get a better idea if
this would be a feasible and clean approach.


Gord

-- 
--------------------------------------------------------------------
Gordon Vreugdenhil,  Staff Engineer               503-685-0808
Model Technology (Mentor Graphics)                gordonv@model.com