While reading the Ptolemy code, I found the following anomaly:
FloydWarshallAllPairShortestPathStrategy implements
AllPairShortestPathAnalyzer.
FloydWarshallCycleExistenceStrategy implements
CycleExistenceAnalyzer.
FloydWarshallNegativeLengthCycleStrategy implements
Can you guys remind me whether there's any architectural
reason to avoid overriding equals() (and hashCode() ) when
writing an actor in Java? Thanks!
Rich Ware
MOCASystems
for the second run fresh, for reasons involving the
nature of my simulation. Does Ptolemy have a way to scrub all actors
out of a model, allowing the creation of new ones?
I look forward to your clarifications.
Richard Ware
Is there a class ptolemy.moml.SharedParameter? Should I be using
ptolemy.actor.parameters.SharedParameter instead?
Posted to the ptolemy-hackers mailing list. Please send administrative
mail for this list to: [EMAIL
Richard Ware wrote:
I'm going to try using a modified form of NamedList, based on the
following:
- Keep all the present code using the internal LinkedList.
- Also keep the named-object references in an internal HashSet,
hashing on the name.
I meant to say, add an internal HashMap
1) It would be frowned on, wouldn't it, for one actor
to fire another directly by calling fireAt(), fireAtRelativeTime()
or fireAtCurrentTime() and giving a reference to the target
actor as an argument to the method call? I figure it would
be frowned on, because in the Ptolemy model actors
to make linking take less time.
Respectfully,
Richard Ware
Posted to the ptolemy-hackers mailing list. Please send administrative
mail for this list to: [EMAIL PROTECTED]