ETSI's Bug Tracker - Part 01: TTCN-3 Core Language
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0006450 | Part 01: TTCN-3 Core Language | Editorial | public | 21-03-2013 20:40 | 11-07-2013 15:43

Reporter | Gyorgy Rethy |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | minor | Reproducibility | always
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v4.6.1 (published 2014-06) | Fixed in Version | v4.6.1 (published 2014-06) |
Clause Reference(s) | 15.11
Source (company - Author) | L.M.Ericsson

Summary | 0006450: Some typos in template concatenation examples
Description | In example 2 of clause 15.11: 1) template RecofChar t_MyRecofChar := {"ABC"} & {"D?", "EF"}; // results the template {"ABC", "D", "EF" } it should be: // results the template {"ABC", "D?", "EF" } 2) template RecofChar t_MyRecofCharPar (integer N):= { "ABC" }, ? * length(N) & { "EF" }; should be: template RecofChar t_MyRecofCharPar (integer N):= { "ABC" }, * length(N) & { "EF" };
Steps To Reproduce |
Additional Information |
Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
21-03-2013 20:40 | Gyorgy Rethy | New Issue |
21-03-2013 20:40 | Gyorgy Rethy | Clause Reference(s) | => 15.11
21-03-2013 20:40 | Gyorgy Rethy | Source (company - Author) | => L.M.Ericsson
21-03-2013 20:41 | Gyorgy Rethy | Summary | Error in concatenation example => Some typos in template concatenation examples
08-07-2013 15:12 | Jens Grabowski | Status | new => assigned
08-07-2013 15:12 | Jens Grabowski | Assigned To | => Ina Schieferdecker
08-07-2013 18:04 | Gyorgy Rethy | Target Version | => v4.6.1 (published 2014-06)
09-07-2013 14:20 | Ina Schieferdecker | Note Added: 0011475 |
09-07-2013 14:35 | Jacob Wieland - Spirent | Note Added: 0011478 |
11-07-2013 10:47 | Ina Schieferdecker | Note Added: 0011533 |
11-07-2013 10:49 | Ina Schieferdecker | Status | assigned => confirmed
11-07-2013 10:49 | Ina Schieferdecker | Status | confirmed => assigned
11-07-2013 10:49 | Ina Schieferdecker | Assigned To | Ina Schieferdecker => Jacob Wieland - Spirent
11-07-2013 12:10 | Jacob Wieland - Spirent | Note Added: 0011542 |
11-07-2013 12:10 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Ina Schieferdecker
11-07-2013 12:10 | Jacob Wieland - Spirent | Status | assigned => confirmed
11-07-2013 15:42 | Ina Schieferdecker | Note Added: 0011552 |
11-07-2013 15:42 | Ina Schieferdecker | Status | confirmed => resolved
11-07-2013 15:42 | Ina Schieferdecker | Fixed in Version | => v4.6.1 (published 2014-06)
11-07-2013 15:42 | Ina Schieferdecker | Resolution | open => fixed
11-07-2013 15:42 | Ina Schieferdecker | Status | resolved => closed

Notes

(0011475)
Ina Schieferdecker
09-07-2013 14:20

As proposed.

(0011478)
Jacob Wieland - Spirent
09-07-2013 14:35

actually, it should be: template RecofChar t_MyRecofCharPar (integer N):= { "ABC" }& ? & * length(N) & { "EF" };

(0011533)
Ina Schieferdecker
11-07-2013 10:47

Indeed, could also be template RecofChar t_MyRecofCharPar (integer N):= { "ABC" } & * length(N) & { "EF" }; Which one is more elaborated for the purpose?

(0011542)
Jacob Wieland - Spirent
11-07-2013 12:10

I think the version whith more features (so with ? & * length) is more elaborate.

(0011552)
Ina Schieferdecker
11-07-2013 15:42

Ok for the more elaborated one, which then results in P.receive ( t_MyRecofCharPar(3) ); //actual content of t_MyRecofCharPar is { "ABC", ?, ?, ?, ?, "EF" }