Logo etsi

ETSI's Bug Tracker

Notice: information submitted on the ETSI issue Tracker may be incorporated in ETSI publication(s) and therefore subject to the ETSI IPR policy.

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0005038ETSI TTCN-3 Quality CheckerT3Q toolpublic01-04-2009 14:4628-04-2009 15:13
ReporterWolfgang Seka 
Assigned ToPhilip Makedonski 
PrioritynormalSeverityfeatureReproducibilityhave not tried
StatusresolvedResolutionduplicate 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0005038: additional naming conventions
Descriptionnew entries for namingConventionsConfig
- local timers (declared within functions)
- local constants (declared within functions)
Question: is there a preferable order (e.g. local constants, timers, variables);
How could this be configured ??

Further naming convnetions:
- modified templates
  (i.e. check that templates which have "modified template" prefix shall have "modifies" statement;
  check that templates not having "modified template" prefix shall not have "modifies" statement)
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0008565)
Philip Makedonski (developer)
28-04-2009 15:13

This issue is split into several issues as it concerns separate quality checks and new discussion issues have been created

>new entries for namingConventionsConfig
>- local timers (declared within functions)
>- local constants (declared within functions)

These fall under naming conventions and are to be discussed under issue 0005129

>Question: is there a preferable order (e.g. local constants, timers, variables);
>How could this be configured ??

This is a separate issue that has to do with the order of local definitions, of which currently only variables are taken into consideration. Configurability suggestions are welcome in the respective issue 0005125

>Further naming convnetions:
>- modified templates
> (i.e. check that templates which have "modified template" prefix shall have >"modifies" statement;
> check that templates not having "modified template" prefix shall not have >"modifies" statement)

These also fall under the naming conventions extension issue (0005129). I believe the second one is redundant as templates *not* having the modifies statement shall comply to the generic template naming conventions.

- Issue History
Date Modified Username Field Change
01-04-2009 14:46 Wolfgang Seka New Issue
01-04-2009 14:46 Wolfgang Seka Status new => assigned
01-04-2009 14:46 Wolfgang Seka Assigned To => Jens Grabowski
03-04-2009 12:32 Philip Makedonski Assigned To Jens Grabowski => Philip Makedonski
28-04-2009 15:13 Philip Makedonski Note Added: 0008565
28-04-2009 15:13 Philip Makedonski Status assigned => resolved
28-04-2009 15:13 Philip Makedonski Resolution open => duplicate
28-04-2009 15:13 Philip Makedonski Projection none => tweak


MantisBT 1.2.14 [^]
Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker