Project

General

Profile

Actions
Copy link

Bug #6629

closed

type resolution problem when using RecordAssembler

Added by Daniel Crawl about 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
High
Assignee:
Marten Lohstroh
Category:
actors
Target version:
-
Start date:
12/01/2014
Due date:
% Done:

100%

Estimated time:
Spent time:
4.25 h
Bugzilla-Id:

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

Download all files
rec-assembler-1.xml (40.1 KB) rec-assembler-1.xml Daniel Crawl, 12/01/2014 04:00 PM
rec-assembler-2.xml (42 KB) rec-assembler-2.xml Daniel Crawl, 12/01/2014 04:00 PM
Actions
Copy link
 #1

Updated by Christopher Brooks about 10 years ago

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

Actions
Copy link
 #2

Updated by Marten Lohstroh almost 10 years ago

  • 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.

Actions
Copy link

Also available in: Atom PDF