In einer eMail vom 9/12/02 12:41:18 PM W. Europe Daylight Time schreibt
This email address is being protected from spambots. You need JavaScript enabled to view it.:
Hi Jacob,
Thanks for your input. It seems that I have interpreted the standard in just
the opposite manner. I think that further
explanatory text should be added in section 14.5 to clarify this.
I am now convinced that your interpretation is the correct one. Thanks!
Cheers,
Claude.
> On Thu, 12 Sep 2002, Claude Desroches wrote:
>
> >
> > Hi Everyone,
> >
> > In TTCN-3 the keyword "template" is introduced (see 14.5 of ES201 873-1
> > V2.2.1(2002-08))
> > for actual parameters.
> >
> > >From my understanding, this would imply that anywhere where "template"
> > appears in a formal parameter definition, that only templates should be
> used.
> > Is this a correct assumption?
>
> No, as template expressions are a superset of value expressions,
> it means - in my understanding of the standard - that all template
> expressions of the parameter type _can_ be used as the actual
> parameter instantiation.
>
> > Conversely, if the keyword "template" is omitted when defining the formal
> > parameters, are templates still permitted, or must the keyword template
> be present for this to be legal TTCN-3 code?
>
> The latter is the case: only real values are permitted
> when the parameter is not declared as "template".
>
Ah yes, you are correct. Based upon the BNF below.
In any case it would be nice to have some clear text explaining this
detail.
168. FunctionActualParList ::= FunctionActualPar {"," FunctionActualPar}
169. FunctionActualPar ::= TimerRef |
TemplateInstance |
Port |
ComponentRef
/* STATIC SEMANTICS - When the corresponding formal parameter is not of
template type the TemplateInstance production shall resolve to one or more
SingleExpressions i.e., equivalent to the Expression production */
> Greetings
Cheers,
Claude.
