Trex-devel October 2006

trex-devel@informatik.uni-goettingen.de

5 participants
3 discussions

template analysis
by Martin Bisanz 24 Oct '06

24 Oct '06

Hi everyone, I'm trying to reimplement the existing template analyses for the TPTP-based smell detection. From my understanding, the following has been implemented so far: - RULE1: unreferenced template -> remove (not yet implemented as refactoring) - RULE2: only 1 reference -> inline template - RULE3: multiple references, no formal parameters ("maximise maintainability") -> inline template - RULE4(?): all references to parameterised template use the same actual paramaters -> inline template params - RULE5: all fields defined by formal parameters -> inline template - RULE6: formal params that aren't actually used -> remove parameter (not yet implemented) Plus the merging rules, but I'm leaving them for now. Comparing these rules with my smell catalogue, I get to the following: RULE 1: Special case of smell "Unused Definition" (I'm going to introduce another subcategory "Unused Definition" with specialized rules "Unused ..." and matching quickfixes/refactorings) RULE 2: "Singular Template Reference" RULE 3: I don't get the point here; why is it considered bad if there are multiple references to a non-parameterized templated? In my opinion, inlining the template leads to duplicated inline templates (which is another smell in my catalogue) RULE 4: Special case of "Unneeded Parameter" (maybe I'll find a more suitable name for this) - same as #1 RULE 5: I haven't had this one yet... But good idea! ;) RULE 6: Special case of "Unused Parameter", same as #1 Can anyone help me with RULE 3? Thanks, Martin

2 1

[Fwd: Re: [Trex-devel] Usage of Scope.resolve() and trunk vs. release]
by Benjamin Zeiss 21 Oct '06

21 Oct '06

-------- Original-Nachricht -------- Betreff: Re: [Trex-devel] Usage of Scope.resolve() and trunk vs. release Datum: Fri, 20 Oct 2006 16:09:29 +0200 (CEST) Von: Jens Bräuer <jensb(a)cs.tu-berlin.de> Antwort an: jensb(a)cs.tu-berlin.de An: Benjamin Zeiss <zeiss(a)cs.uni-goettingen.de> Referenzen: <BAY13-F206A1721A5B4BEBBABFD50B90E0(a)phx.gbl> <29843.194.114.62.34.1161273889.squirrel(a)www.muppet-show> <4537AF86.4090408(a)cs.uni-goettingen.de> Hi Benjamin, >> And: Any plans when semanticalAnalysis will be back again ? ;-) > > Our development resources for TRex are currently very limited. So i > don't want to promise anything. The problem is that currently, the > semantical analysis reports false errors in the scope visibility > analysis (in the SIP test suite for example), because we don't have the > TTCN-3 built-in functions implemented (int2str etc.). Hence, it is > currently disabled until someone addresses this issue. The issues isn't > too big though. > There seems to be another problem when using the current version of semanticalAnalysis. Variables declared in the component are not resolved properly. Had a look onto TTCN3SymbolTableTreeParser but i was unable to find anything useful. The below example produces: 1079 [main] WARN de.tuberlin.cs.jensb - D:\jbr\svn_trunk_uni\code\TRexTest\src\de\tuberlin\cs\jensb\01.ttcn3:13:0: j is not declared When logging the exceptions via log4j. [Sample posted again for completeness] >> --- 01.ttcn3 --- >> module test { >> type component A { >> var integer j; >> var integer i; >> } >> >> testcase foo() runs on A { >> var integer i := 0; >> j := i; >> } >> >> control { >> execute(foo()); >> } >> } >> --- /01.ttcn3 --- > by the way: the website here contains some additional maybe useful > documentation on the symbol table stuff. > > http://www.trex.informatik.uni-goettingen.de/trac/wiki/SymbolTableDocumenta… Already had a look on it and i clearly states, that resolve(String) is deprecated. ;-) Sorry, that i missed that point. Greetings, Jens -- Benjamin Zeiss Institute for Informatics http://www.swe.informatik.uni-goettingen.de University Goettingen, Lotzestr. 16-18 phone: +49 551 39 14695 D-37073 Goettingen, Germany fax: +49 551 39 14415

2 4

ASN.1 support for TRex
by FC FCBetterThanWindows 19 Oct '06

19 Oct '06

Hi I have seen that there exist also ASN.1 plugin for eclipse http://sourceforge.net/projects/asneditor/. Could it also be integrated into the TRex? Then also in Tau integration, ASN.1 has been left out as the files what are passed down from project to the Tau compiler do not contain any ASN.1 files even if I have them in project. Also it seems that in the Tau integeration it is not possible to define any Tau compiler flags nowhere. Probably should be through the TRex->Window->Pref as there is also the path to Tau. BR TC _________________________________________________________________ Don't just search. Find. Check out the new MSN Search! http://search.msn.com/

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Trex-devel October 2006