Yes. An interface class defines a set of virtual methods that the implementing class provides. The various qualifiers don't make sense for the interface class nor would they really make any sense for the implementing class in terms of why you would want to specify a interface class type in the first place -- to have a handle to "anything" that implements the interface class. That concept doesn't compose well with "protected" or "local". Gord On 1/5/16 3:39 AM, Shalom Bresticker wrote: > > In classes, a pure virtual method declaration can have a > class_item_qualifier: > > class_method ::= > > … > > | *pure virtual *{ class_item_qualifier } method_prototype *;* > > class_item_qualifier8 ::= > > *static* > > | *protected* > > | *local* > > In an interface class, a pure virtual method declaration may not: > > interface_class_item ::= > > … > > | { attribute_instance } interface_class_method > > interface_class_method ::= > > *pure virtual *method_prototype *;* > > ** > > Is this deliberate? > > Thanks, > > Shalom > -- -------------------------------------------------------------------- Gordon Vreugdenhil 503-685-0808 Verification Technologies, Mentor Graphics gordonv@model.comReceived on Tue Jan 5 06:42:17 2016
This archive was generated by hypermail 2.1.8 : Tue Jan 05 2016 - 06:42:32 PST