Trex-devel

trex-devel@informatik.uni-goettingen.de

50 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

Non-JDT/PDE natures in .project files of TRex sources
by Helmut Neukirchen 05 Sep '06

05 Sep '06

Dear all, while reviewing the changes of the last week, I stumbled over changeset 743 which adds to file de.ugoe.cs.swe.trex.ui/.project the following natures (probably from the VE plugin): <nature>org.eclipse.jem.workbench.JavaEMFNature</nature> <nature>org.eclipse.jem.beaninfo.BeanInfoNature</nature> I do not know whether we shall remove these lines or just keep them since sooner or later they will probably slip in again. Since they do not provoke any errors if VE is not installed, we might decide to keep them. On the other hands, these natures are not required to build TRex from the sources and thus only clutter up the .project file. Any opinions? On behalf of the dotfile police, Helmut -- Helmut Neukirchen mailto:neukirchen@informatik.uni-goettingen.de Institute for Informatics http://www.swe.informatik.uni-goettingen.de University of Göttingen, Lotzestr. 16-18 phone: +49 551 39 14695 D-37083 Göttingen, Germany fax: +49 551 39 14415

2 2

Documentation of enabled debug messages
by Helmut Neukirchen 05 Sep '06

05 Sep '06

Hi Benjamin, in http://www.trex.informatik.uni-goettingen.de/jira/browse/TTC-232 you wrote "In addition to this, i am right now enabling the our debug messages for the nightly builds. You may try this again tomorrow (when the nightly build includes this change) with a new nightly build and start eclipse with -debug." I think we should document 1. this property of the nightly builds on the Download page 2. in the "How to release a new release of TRex?" HOWTO that those messages shall be disabled in the .options file of release version (or shall we keep that options enabled for the releases as well since the -debug option needs to be provided anyway to enable tracing?) shouldn't we? Bye, Helmut -- Helmut Neukirchen mailto:neukirchen@informatik.uni-goettingen.de Institute for Informatics http://www.swe.informatik.uni-goettingen.de University of Göttingen, Lotzestr. 16-18 phone: +49 551 39 14695 D-37083 Göttingen, Germany fax: +49 551 39 14415

2 1

Re: [Trex-devel] LocationAST.equals(AST)
by Benjamin Zeiss 30 Aug '06

30 Aug '06

Hi Martin, > My proposal is to change LocationAST not to overwrite > BaseAST.equals(AST), but to introduce a new method, say > equalsIncludingLocation(LocationAST), and change all references > accordingly. i am actually not that sure about it, because it might lead to errors or problems because other programmers are not aware of this detail and they just use equals, because they expect it to work properly (and just comparing text might not always be enough). although it is less elegant, i think i would therefore go the other way and copy equalstree and replace this.equals with another function. -- Benjamin Zeiss

2 1

LocationAST.equals(AST)
by Martin Bisanz 30 Aug '06

30 Aug '06

Hi everybody, in order to look for duplicated code I'd like to compare subtrees and sequences (i.e. subtrees without root node) with each other. Two subtrees should be equal to each other if types and texts of all nodes in the trees are equal. I found some methods (equalsTree(AST) and equalsList(AST)) in BaseAST which do exactly this. However, they use BaseAST.equals(AST). Unfortunately, this method is overwritten in LocationAST and additionally compares the line and column of the node - which is pretty useless for my purpose. My proposal is to change LocationAST not to overwrite BaseAST.equals(AST), but to introduce a new method, say equalsIncludingLocation(LocationAST), and change all references accordingly. Any objections? Thanks, Martin

1 0

compiler integration
by Benjamin Zeiss 24 Aug '06

24 Aug '06

hi, i want to approach the compiler integration thing soon. Therefore, i want to discuss how we should realize that. There are several ways to approach this: 1) Don't use the builder framework and realize it like it is now (maybe move the tau stuff to its own plugin) 2) Use the builder framework. * allow several builder plugins to be installed at a time -> do we allow compilation using several compilers in one run -> should only one compiler be active * allow only one builder plugin to be installed at a time Lets assume we want 2). The first choice (allow several builder plugins to be installed at a time) requires our own extension point. The builder would be implemented in TRex UI and it would delegate its work to corresponding builder plugins. However, it requires a preference page where the compilers are selectable/chooseable and addition to the preference pages for the compiler options. This page would not be necessary if only one builder plugin would be allowed to be installed at a time. Another thing to discuss is, what the builder is supposed to do. Tau currently has three options: Analyze, Compile, Create Executable. How should this be handled in a builder: * Make the builder configurable, e.g. configure the builder not to compile * The builder always compiles everything Then again, depending on the compiler, it may not be possible to differentiate the step compilation and create executable (this seems to be the case with danet). Concerning the executable building: currently, the exeutable is built from the currently active or selected file or something like that i suppose. This is probably not a good idea when the builder is used since the default Eclipse behavior is that we would expect the project to be built and not the active file. Hence, there must be a project property page or yet another navigator label decorator where modules with control parts can be selected for executable building. I guess there are tons of other decisions that i am missing in these first thoughts, but it should be enough to start the discussion. -- Benjamin Zeiss

2 3

Release planning
by Helmut Neukirchen 22 Aug '06

22 Aug '06

Dear all, after releasing TRex 0.5.3, we intended to head directly for TRex 0.6.0, unless there are no critical bugs which require a 0.5.4 release. Now, I just realised that two feature requests are explicitely scheduled in JIRA for 0.5.4 by Benjamin. I have no problems with this, but I just like to document via this email that we aim at 0.5.4. Benjamin, is that what you intend? If yes, I will re-schedule the already fixed bugs (in particular TTC-222) from 0.6.0 to 0.5.4. Bye, Helmut -- Helmut Neukirchen mailto:neukirchen@informatik.uni-goettingen.de Institute for Informatics http://www.swe.informatik.uni-goettingen.de University of Göttingen, Lotzestr. 16-18 phone: +49 551 39 14695 D-37083 Göttingen, Germany fax: +49 551 39 14415

2 6

Nightly Builds
by Dominic Evans 04 Aug '06

04 Aug '06

Hi, At what time (and in which timezone) does the nightly build get generated? Is it simple to manually cause this build to be regenerated? I committed some fixes and optimisations just now and would like to seed them to a user in the US. Rather than manually sending them a .jar it would be ideal if I could just get them to re-sync with the nightly update site. Best regards, Dominic

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Trex-devel