Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: BNF Non-terminals are still called teststep

BNF Non-terminals are still called teststep 27 Mar 2002 10:12 #6118

Hi,

I just browsed the recently distributed TTCN-3 core document (ETSI ES 201
873-1 V2.2.0 (2002-03)) and realized that although teststeps (and the BNF
terminals) have been renamed to altsteps the non-terminals in the BNF still
refer to teststeps.

Was this intended?

>A.1.6.1.7 Altstep Definitions
>192. TeststepDef ::= TeststepKeyword TeststepIdentifier
>"("[TeststepFormalParList] ")" [RunsOnSpec]
>BeginChar
>TeststepLocalDefList
>AltGuardList
>EndChar
>193. TeststepKeyword ::= "altstep"
>194. TeststepIdentifier ::= Identifier
>195. TeststepFormalParList ::= FunctionFormalParList
>/* STATIC SEMANTICS - all formal parameter must be value parameters i.e.,
>in parameters */
>196. TeststepLocalDefList ::= {TeststepLocalDef [SemiColon]}
>197. TeststepLocalDef ::= VarInstance | TimerInstance | ConstDef
>198. TeststepInstance ::= TeststepRef "(" [FunctionActualParList] ")"
>199. TeststepRef ::= [GlobalModuleId Dot] TeststepIdentifier

I can imagine that every reference to teststep could be safely replaced
with altstep, or? Esp. Rule 193. is a little bit confusing, or?

Ciao

Theo

Theofanis Vassiliou-Gioles Testing Technologies IST GmbH
This email address is being protected from spambots. You need JavaScript enabled to view it. Oranienburger Str. 65, 10117 Berlin
phone: +49 30 726 19 19 0 web: www.testingtech.de
The administrator has disabled public write access.

BNF Non-terminals are still called teststep 27 Mar 2002 10:49 #6120

Hi,

Not intentional; it is corrected to Altstep... in the latest draft (will be available soon).

Best Regards, György
Szia, Gyuri
============================================
dr. György RÉTHY
Ericsson Communications Systems Hungary Lim.
Conformance Center
tel.: +36 1 437-7006; fax: +36 1 437-7767
mobile: +36 30 297-7862
e-mail: This email address is being protected from spambots. You need JavaScript enabled to view it.
intranet: conformancelab.ericsson.se
personal: www.r.eth.ericsson.se/~ethgry
============================================


>
Original Message
>From: Theofanis Vassiliou-Gioles [This email address is being protected from spambots. You need JavaScript enabled to view it.]
>Sent: Wednesday, March 27, 2002 11:12 AM
>To: This email address is being protected from spambots. You need JavaScript enabled to view it.
>Subject: BNF Non-terminals are still called teststep
>
>
>Hi,
>
>I just browsed the recently distributed TTCN-3 core document
>(ETSI ES 201
>873-1 V2.2.0 (2002-03)) and realized that although teststeps
>(and the BNF
>terminals) have been renamed to altsteps the non-terminals in
>the BNF still
>refer to teststeps.
>
>Was this intended?
>
>>A.1.6.1.7 Altstep Definitions
>>192. TeststepDef ::= TeststepKeyword TeststepIdentifier
>>"("[TeststepFormalParList] ")" [RunsOnSpec]
>>BeginChar
>>TeststepLocalDefList
>>AltGuardList
>>EndChar
>>193. TeststepKeyword ::= "altstep"
>>194. TeststepIdentifier ::= Identifier
>>195. TeststepFormalParList ::= FunctionFormalParList
>>/* STATIC SEMANTICS - all formal parameter must be value
>parameters i.e.,
>>in parameters */
>>196. TeststepLocalDefList ::= {TeststepLocalDef [SemiColon]}
>>197. TeststepLocalDef ::= VarInstance | TimerInstance | ConstDef
>>198. TeststepInstance ::= TeststepRef "(" [FunctionActualParList] ")"
>>199. TeststepRef ::= [GlobalModuleId Dot] TeststepIdentifier
>
>I can imagine that every reference to teststep could be safely replaced
>with altstep, or? Esp. Rule 193. is a little bit confusing, or?
>
>Ciao
>
>Theo
>
>
>Theofanis Vassiliou-Gioles Testing Technologies IST GmbH
>This email address is being protected from spambots. You need JavaScript enabled to view it. Oranienburger Str. 65, 10117 Berlin
>phone: +49 30 726 19 19 0 web: www.testingtech.de
>
The administrator has disabled public write access.

BNF Non-terminals are still called teststep 27 Mar 2002 10:50 #6121

Hi,
Please ignore my last email, as I referred to an outdated version.
Sorry for the confusion.

Best regards,

Theo

At 11:12 27.03.2002, Theofanis Vassiliou-Gioles wrote:
>Hi,
>
>I just browsed the recently distributed TTCN-3 core document (ETSI ES 201
>873-1 V2.2.0 (2002-03)) and realized that although teststeps (and the BNF
>terminals) have been renamed to altsteps the non-terminals in the BNF still
>refer to teststeps.
>
>Was this intended?
>
>>A.1.6.1.7 Altstep Definitions
>>192. TeststepDef ::= TeststepKeyword TeststepIdentifier
>>"("[TeststepFormalParList] ")" [RunsOnSpec]
>>BeginChar
>>TeststepLocalDefList
>>AltGuardList
>>EndChar
>>193. TeststepKeyword ::= "altstep"
>>194. TeststepIdentifier ::= Identifier
>>195. TeststepFormalParList ::= FunctionFormalParList
>>/* STATIC SEMANTICS - all formal parameter must be value parameters i.e.,
>>in parameters */
>>196. TeststepLocalDefList ::= {TeststepLocalDef [SemiColon]}
>>197. TeststepLocalDef ::= VarInstance | TimerInstance | ConstDef
>>198. TeststepInstance ::= TeststepRef "(" [FunctionActualParList] ")"
>>199. TeststepRef ::= [GlobalModuleId Dot] TeststepIdentifier
>
>I can imagine that every reference to teststep could be safely replaced
>with altstep, or? Esp. Rule 193. is a little bit confusing, or?
>
>Ciao
>
>Theo
>
>
>Theofanis Vassiliou-Gioles Testing Technologies IST GmbH
>This email address is being protected from spambots. You need JavaScript enabled to view it. Oranienburger Str. 65, 10117 Berlin
>phone: +49 30 726 19 19 0 web: www.testingtech.de
The administrator has disabled public write access.
  • Page:
  • 1

FacebookTwitterGoogle BookmarksRedditNewsvineTechnoratiLinkedin