Bug #6629
closed
type resolution problem when using RecordAssembler
Added by Daniel Crawl almost 10 years ago.
Updated almost 10 years ago.
Description
Using RecordAssembler can cause type resolution to fail. Attached are two models that demonstrate the problem.
In rec-assembler-1.xml, a type resolution error will usually, but not always, occur when you run it.
In rec-assembler-2.xml, the second RecordAssembler actor is replaced with an Expression actor that constructs the same record, and no type resolution error occurs.
Files
This seems like a simple use of RecordAssembler that should work. I checked in a test for this at $PTII/ptolemy/actor/lib/test/auto/RecordAssemblerTypeError.xml
- Status changed from New to Closed
- Assignee changed from Daniel Crawl to Marten Lohstroh
- % Done changed from 0 to 100
The arbitrary order in which Mogensen's algorithm resolves type constraints seemed to trigger non-deterministic type errors due to an error in ParseTreeTypeInference.visitMethodCallNode(). Changes were made in revision 71540 and the supplied model now runs without errors.
Also available in: Atom
PDF