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

TOPIC: Most common TTCN-3 errors done at the moment

Most common TTCN-3 errors done at the moment 14 Oct 2003 11:29 #6530

Hello all TTCN-3 users!

We have collected a list of most common errors we have found
people are doing when they write TTCN-3 modules and made
this information available in our website as HTML & PDF:

www.openttcn.com/Sections/News/Top5_TTCN3_Errors/

If you have ideas of other commonly made errors, please let us know!

Best regards,
Vesa-Matti
The administrator has disabled public write access.

Most common TTCN-3 errors done at the moment 14 Oct 2003 13:42 #6531

Dear Vesa,

thank you for this interesting list - I just have one minor comment: it
is allowed to use the activate without binding its result to a
defaulttype variable - like you can have an execute without binding its
result to a verdicttype variable.

Cheers, Ina.

Vesa-Matti Puro wrote:
> Hello all TTCN-3 users!
>
> We have collected a list of most common errors we have found
> people are doing when they write TTCN-3 modules and made
> this information available in our website as HTML & PDF:
>
> www.openttcn.com/Sections/News/Top5_TTCN3_Errors/
>
> If you have ideas of other commonly made errors, please let us know!
>
> Best regards,
> Vesa-Matti


--
Ina Schieferdecker
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241
The administrator has disabled public write access.

Most common TTCN-3 errors done at the moment 14 Oct 2003 13:56 #6532

Dear Ina,

Thank you for your comments.

I agree that it is possible to have an execute & function call without
binding their results to a variable.

But when you say that it is possible to have an activate without binding
it results, do you refer to the current published standard, or some CR?
In the BNF of the ETSI ES 201 873-1 V 2.2.1 (2003-02) we have not
spotted that kind of possiblity. Which BNF rules do you refer?

Best regards,
Vesa-Matti

Ina Schieferdecker wrote:
> Dear Vesa,
>
> thank you for this interesting list - I just have one minor comment: it
> is allowed to use the activate without binding its result to a
> defaulttype variable - like you can have an execute without binding its
> result to a verdicttype variable.
>
> Cheers, Ina.
>
> Vesa-Matti Puro wrote:
> > Hello all TTCN-3 users!
> >
> > We have collected a list of most common errors we have found
> > people are doing when they write TTCN-3 modules and made
> > this information available in our website as HTML & PDF:
> >
> > www.openttcn.com/Sections/News/Top5_TTCN3_Errors/
> >
> > If you have ideas of other commonly made errors, please let us know!
> >
> > Best regards,
> > Vesa-Matti
>
>
> --
>
> Ina Schieferdecker
> Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
> Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
> D-10589 Berlin fax: ++49-30-3463-8241
>

--
Vesa-Matti Puro
E-mail: This email address is being protected from spambots. You need JavaScript enabled to view it.
Tel.: +358 440396461
OpenTTCN Oy
Web: www.openttcn.com
The administrator has disabled public write access.

Most common TTCN-3 errors done at the moment 14 Oct 2003 14:23 #6533

Deare Vesa-Matti,

indeed it is the CR 206 on "Activate operation without mandatory
assignment of result", which was accepted.

This has lead to the addition of ActivateOp in behavior statements:

A.1.6.7 Behaviour Statements
BehaviourStatements ::=
TestcaseInstance |
FunctionInstance |
ReturnStatement |
AltConstruct |
InterleavedConstruct |
LabelStatement |
GotoStatement |
RepeatStatement |
DeactivateStatement |
AltstepInstance |
ActivateOp

Cheers, Ina.


Vesa-Matti Puro wrote:
> Dear Ina,
>
> Thank you for your comments.
>
> I agree that it is possible to have an execute & function call without
> binding their results to a variable.
>
> But when you say that it is possible to have an activate without binding
> it results, do you refer to the current published standard, or some CR?
> In the BNF of the ETSI ES 201 873-1 V 2.2.1 (2003-02) we have not
> spotted that kind of possiblity. Which BNF rules do you refer?
>
> Best regards,
> Vesa-Matti
>
> Ina Schieferdecker wrote:
>
>> Dear Vesa,
>>
>> thank you for this interesting list - I just have one minor comment: it
>> is allowed to use the activate without binding its result to a
>> defaulttype variable - like you can have an execute without binding its
>> result to a verdicttype variable.
>>
>> Cheers, Ina.
>>
>> Vesa-Matti Puro wrote:
>> > Hello all TTCN-3 users!
>> >
>> > We have collected a list of most common errors we have found
>> > people are doing when they write TTCN-3 modules and made
>> > this information available in our website as HTML & PDF:
>> >
>> > www.openttcn.com/Sections/News/Top5_TTCN3_Errors/
>> >
>> > If you have ideas of other commonly made errors, please let us know!
>> >
>> > Best regards,
>> > Vesa-Matti
>>
>>
>> --
>>
>> Ina Schieferdecker
>> Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
>> Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
>> D-10589 Berlin fax: ++49-30-3463-8241
>>
>
>
> --
> Vesa-Matti Puro
> E-mail: This email address is being protected from spambots. You need JavaScript enabled to view it.
> Tel.: +358 440396461
> OpenTTCN Oy
> Web: www.openttcn.com


--
Ina Schieferdecker
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241
The administrator has disabled public write access.

Most common TTCN-3 errors done at the moment 15 Oct 2003 10:24 #6534

Dear Ina,

I can make that note to the document immediately that there exists
a CR about the matter, and that it is already accepted.


The ETSI page says currently about CR 206:

206 Activate operation without mandatory assignment of result
Mariusz Kupiec 2.2.1 Core Minor Technical
Entered: 17 Dec 2003
Status: entered review by team members


So in that sense the error description about the use of activate
still holds as there seems to be at least four different truths
about he matter:

1. ETSI web-site saying that the CR 206 is in "entered review by team
members" status == the published standard is the last info

2. Ina reports that the CR 206 is accepted == activate without
assignment of the return value can be used

3. The published and current valid TTCN-3 standard says that
active needs the assignment for its return value

4. Some ealier standard said another thing...


The conclusion is that TTCN-3 users make mistakes because
of mixing past and present standards, and made CRs, accepted
CRs, and accepted and reported accptance of CRs by ETSI.

Best regards,
Vesa-Matti


Ina Schieferdecker wrote:
> Deare Vesa-Matti,
>
> indeed it is the CR 206 on "Activate operation without mandatory
> assignment of result", which was accepted.
>
> This has lead to the addition of ActivateOp in behavior statements:
>
> A.1.6.7 Behaviour Statements
> BehaviourStatements ::=
> TestcaseInstance |
> FunctionInstance |
> ReturnStatement |
> AltConstruct |
> InterleavedConstruct |
> LabelStatement |
> GotoStatement |
> RepeatStatement |
> DeactivateStatement |
> AltstepInstance |
> ActivateOp
>
> Cheers, Ina.
>
>
> Vesa-Matti Puro wrote:
> > Dear Ina,
> >
> > Thank you for your comments.
> >
> > I agree that it is possible to have an execute & function call without
> > binding their results to a variable.
> >
> > But when you say that it is possible to have an activate without binding
> > it results, do you refer to the current published standard, or some CR?
> > In the BNF of the ETSI ES 201 873-1 V 2.2.1 (2003-02) we have not
> > spotted that kind of possiblity. Which BNF rules do you refer?
> >
> > Best regards,
> > Vesa-Matti
> >
> > Ina Schieferdecker wrote:
> >
> >> Dear Vesa,
> >>
> >> thank you for this interesting list - I just have one minor comment: it
> >> is allowed to use the activate without binding its result to a
> >> defaulttype variable - like you can have an execute without binding its
> >> result to a verdicttype variable.
> >>
> >> Cheers, Ina.
> >>
> >> Vesa-Matti Puro wrote:
> >> > Hello all TTCN-3 users!
> >> >
> >> > We have collected a list of most common errors we have found
> >> > people are doing when they write TTCN-3 modules and made
> >> > this information available in our website as HTML & PDF:
> >> >
> >> > www.openttcn.com/Sections/News/Top5_TTCN3_Errors/
> >> >
> >> > If you have ideas of other commonly made errors, please let us know!
> >> >
> >> > Best regards,
> >> > Vesa-Matti
> >>
> >>
> >> --
> >>
> >> Ina Schieferdecker
> >> Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
> >> Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
> >> D-10589 Berlin fax: ++49-30-3463-8241
> >>
> >
> >
> > --
> > Vesa-Matti Puro
> > E-mail: This email address is being protected from spambots. You need JavaScript enabled to view it.
> > Tel.: +358 440396461
> > OpenTTCN Oy
> > Web: www.openttcn.com
>
>
> --
>
> Ina Schieferdecker
> Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
> Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
> D-10589 Berlin fax: ++49-30-3463-8241
>

--
Vesa-Matti Puro
E-mail: This email address is being protected from spambots. You need JavaScript enabled to view it.
Tel.: +358 440396461
OpenTTCN Oy
Web: www.openttcn.com
The administrator has disabled public write access.

Most common TTCN-3 errors done at the moment 23 Oct 2003 08:28 #6544

Dear Vesa-Matti,

I can only support your view.

We now agreed within the maintenance STF to make not only an up-to-date
CR table, but also the CRs together with their revisions, and the
mock-up version for TTCN-3 available on the Web. However, it may take a
while as the ETSI Web pages are currently being reorganized.

Sorry that we cannot do better than this.

With best regards,

Ina.

Vesa-Matti Puro wrote:
> Dear Ina,
>
> I can make that note to the document immediately that there exists
> a CR about the matter, and that it is already accepted.
>
>
> The ETSI page says currently about CR 206:
>
> 206 Activate operation without mandatory assignment of result
> Mariusz Kupiec 2.2.1 Core Minor Technical
> Entered: 17 Dec 2003
> Status: entered review by team members
>
>
> So in that sense the error description about the use of activate
> still holds as there seems to be at least four different truths
> about he matter:
>
> 1. ETSI web-site saying that the CR 206 is in "entered review by team
> members" status == the published standard is the last info
>
> 2. Ina reports that the CR 206 is accepted == activate without
> assignment of the return value can be used
>
> 3. The published and current valid TTCN-3 standard says that
> active needs the assignment for its return value
>
> 4. Some ealier standard said another thing...
>
>
> The conclusion is that TTCN-3 users make mistakes because
> of mixing past and present standards, and made CRs, accepted
> CRs, and accepted and reported accptance of CRs by ETSI.
>
> Best regards,
> Vesa-Matti
>
>
> Ina Schieferdecker wrote:
>
>> Deare Vesa-Matti,
>>
>> indeed it is the CR 206 on "Activate operation without mandatory
>> assignment of result", which was accepted.
>>
>> This has lead to the addition of ActivateOp in behavior statements:
>>
>> A.1.6.7 Behaviour Statements
>> BehaviourStatements ::=
>> TestcaseInstance |
>> FunctionInstance |
>> ReturnStatement |
>> AltConstruct |
>> InterleavedConstruct |
>> LabelStatement |
>> GotoStatement |
>> RepeatStatement |
>> DeactivateStatement |
>> AltstepInstance |
>> ActivateOp
>>
>> Cheers, Ina.
>>
>>
>> Vesa-Matti Puro wrote:
>> > Dear Ina,
>> >
>> > Thank you for your comments.
>> >
>> > I agree that it is possible to have an execute & function call without
>> > binding their results to a variable.
>> >
>> > But when you say that it is possible to have an activate without
>> binding
>> > it results, do you refer to the current published standard, or some
>> CR?
>> > In the BNF of the ETSI ES 201 873-1 V 2.2.1 (2003-02) we have not
>> > spotted that kind of possiblity. Which BNF rules do you refer?
>> >
>> > Best regards,
>> > Vesa-Matti
>> >
>> > Ina Schieferdecker wrote:
>> >
>> >> Dear Vesa,
>> >>
>> >> thank you for this interesting list - I just have one minor
>> comment: it
>> >> is allowed to use the activate without binding its result to a
>> >> defaulttype variable - like you can have an execute without
>> binding its
>> >> result to a verdicttype variable.
>> >>
>> >> Cheers, Ina.
>> >>
>> >> Vesa-Matti Puro wrote:
>> >> > Hello all TTCN-3 users!
>> >> >
>> >> > We have collected a list of most common errors we have found
>> >> > people are doing when they write TTCN-3 modules and made
>> >> > this information available in our website as HTML & PDF:
>> >> >
>> >> > www.openttcn.com/Sections/News/Top5_TTCN3_Errors/
>> >> >
>> >> > If you have ideas of other commonly made errors, please let us
>> know!
>> >> >
>> >> > Best regards,
>> >> > Vesa-Matti
>> >>
>> >>
>> >> --
>> >>
>>
>> >> Ina Schieferdecker
>> >> Fraunhofer FOKUS email:
>> This email address is being protected from spambots. You need JavaScript enabled to view it.
>> >> Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
>> >> D-10589 Berlin fax: ++49-30-3463-8241
>> >>
>>
>> >
>> >
>> > --
>> > Vesa-Matti Puro
>> > E-mail: This email address is being protected from spambots. You need JavaScript enabled to view it.
>> > Tel.: +358 440396461
>> > OpenTTCN Oy
>> > Web: www.openttcn.com
>>
>>
>> --
>>
>> Ina Schieferdecker
>> Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
>> Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
>> D-10589 Berlin fax: ++49-30-3463-8241
>>
>
>
> --
> Vesa-Matti Puro
> E-mail: This email address is being protected from spambots. You need JavaScript enabled to view it.
> Tel.: +358 440396461
> OpenTTCN Oy
> Web: www.openttcn.com


--
Ina Schieferdecker
Fraunhofer FOKUS email: This email address is being protected from spambots. You need JavaScript enabled to view it.
Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241
D-10589 Berlin fax: ++49-30-3463-8241
The administrator has disabled public write access.
  • Page:
  • 1

FacebookTwitterGoogle BookmarksRedditNewsvineTechnoratiLinkedin