This issue tracker is closed. Please visit UPPAAL issue tracker at Github instead.

Bug 268 - Function local variables not recognized as non-compile time values
Summary: Function local variables not recognized as non-compile time values
Status: RESOLVED FIXED
Alias: None
Product: UPPAAL
Classification: Unclassified
Component: libutap (show other bugs)
Version: 3.6 Alpha 4
Hardware: All All
: P1 major
Assignee: Gerd Behrmann
URL:
Depends on:
Blocks:
 
Reported: 2006-02-13 19:36 CET by Gerd Behrmann
Modified: 2006-02-20 20:18 CET (History)
0 users

See Also:
Architecture:

Attachments
Test case (601 bytes, application/xml)
2006-02-13 19:36 CET, Gerd Behrmann 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gerd Behrmann 2006-02-13 19:36:12 CET 
In general the value of function local integer variables is not known at compile time. Therefore they must 
not be allowed in integer range specifications or arrays size specifications. Yes, such mistakes are not 
detected by the type checker.
Comment 1 Gerd Behrmann 2006-02-13 19:36:50 CET 
Created attachment 87 [details]
Test case

Test case using a function local integer in array declaration inside a
function.
Comment 2 Gerd Behrmann 2006-02-20 20:18:23 CET 
Fixed on the trunk (rev. 1541).