#3199 closed defect (invalid)
ParModelica does not expect usage of parallel variables
Reported by: | Gustaf Thorslund | Owned by: | Mahder Alemseged Gebremedhin |
---|---|---|---|
Priority: | high | Milestone: | never |
Component: | ParModelica | Version: | trunk |
Keywords: | ParModelica | Cc: |
Description (last modified by )
Given a slightly updated exampled like:
function parvar input Integer m = 1000; input Integer A[m]; input Integer B[m]; protected Integer q; parallel Integer pm; // <-- Error: Missing token: FUNCTION parallel Integer pn; parallel Integer pA[m]; parallel Integer pB[m]; end parvar;
Trying to compile it using ParModelica gives:
$ omc -g=ParModelica parvar.mo Error processing file: parvar.mo Failed to parse file: parvar.mo! [/home/gustaf/kurser/exjobb/test/parmodelica/parvar.mo:7:12-7:12:writable] Error: Missing token: FUNCTION # Error encountered! Exiting... # Please check the error message and the flags. Failed to parse file: parvar.mo! Execution failed!
$ omc --version
1.9.2+dev (r24991)
Change History (5)
comment:1 by , 10 years ago
Description: | modified (diff) |
---|
comment:2 by , 10 years ago
comment:3 by , 10 years ago
:)
You can use this presentation as a temporary user guide until I get you a proper documentation for it.
comment:5 by , 9 years ago
Milestone: | Future → never |
---|
Sorting away the closed as invalid, won't fix and duplicate tickets from Future.
Note:
See TracTickets
for help on using tickets.
Somehow I heard a bird whisper down the corridor, telling me I should have used parglobal and parlocal instead of parallel. C'est la vie.
So this ticket is now rather a documentation bug, where the user should read some newer presentation instead of the old thesis to get the right keywords.
I'll let the bird figure out where else to spread the news.