-------- 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@cs.tu-berlin.de Antwort an: jensb@cs.tu-berlin.de An: Benjamin Zeiss zeiss@cs.uni-goettingen.de Referenzen: BAY13-F206A1721A5B4BEBBABFD50B90E0@phx.gbl 29843.194.114.62.34.1161273889.squirrel@www.muppet-show 4537AF86.4090408@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/SymbolTableDocumentat...
Already had a look on it and i clearly states, that resolve(String) is deprecated. ;-) Sorry, that i missed that point.
Greetings, Jens