Subject: RE: interface gate restriction
anders.ek#telelogic.se
Date: Thu Jan 25 2001 - 06:46:26 GMT
A problem might be that there would be a circular definition. The implicit
interface of an agent inherits from the interfaces in the incoming signal
lists. So if we put the implicit interface in the signal list, it would
inherit from itself.
/Anders
> -----Original Message-----
> From: Rick Reed TSE [mailto:rickreed#tseng.co.uk]
> Sent: den 24 januari 2001 21:51
> To: meeting
> Subject: interface gate restriction
>
>
> In 8.1.6 Gate Concrete Textual Grammar there is a condition:
>
> "The <interface identifier> of an <textual interface gate
> definition> must
> not identify the interface implicitly defined by the entity
> to which the
> gate is connected (see 12.1.2)."
>
> I do not understand why this restriction exists:
>
> a) the implicit interface does not define an implicit gate
> (not that I could
> find in Z.100 - if I am wrong please point out where this is defined);
>
> b) in any case, another interface can be defined that
> inherits the implicit
> interface, which would have the same effect;
>
> c) the restriction does not exist for <graphical interface
> gate definition>;
>
> d) it would be possible to define a named gate with the interface as a
> signal list.
>
> Perhaps it was intended the implicit interface defines an
> implicit gate
> (with the same name as the interface, which is the same name
> as the entity).
> However, in this case the restriction is not needed, because
> there would be
> a clash of names if an explicit definition is given.
>
> Does anyone have an explanation, what this condition is for?
>
> As the gate is not implicitly defined, it seems reasonable
> that it should be
> allowed to explicitly define such a gate.
>
> --
> Rick Reed - rickreed#tseng.co.uk
> Tel:+44 1455 55 96 55 Fax:+44 1455 55 96 58 Mob.:+44 7970 50 96 50
>
>
This archive was generated by hypermail 2a23 : Mon May 05 2008 - 20:30:55 GMT