[kepler-dev] programatic access to class entity
Edward A. Lee
eal at eecs.berkeley.edu
Wed Jul 27 08:05:34 PDT 2005
The <class> tag is defined in section 2.7 of vol. 1 of the Ptolemy II docs.
An entity that is defined as a <class> can be instantiated many times,
without copying its contents. Any changes made to the class will be made
to all the instances. It can also be subclassed.
We call this mechanism "actor-oriented classes" to distinguish them
from the "object-oriented classes" of Java. It brings the OO concept
of inheritance to actor-oriented designs. There is a paper on it
At 03:20 PM 7/20/2005 -0700, Chad Berkley wrote:
>does anyone know what the programatic difference is between an entity
>that is defined in moml as <entity> vs. one that's defined as <class>?
>I need to figure out the difference in the KSW builder, but i can't see
>where in the MoML API you can get information as (AFAICT) they both get
>instantiated as a ComponentEntity. Basically, i just want to know how
>to tell the difference (programatically) between a stand alone workflow
>and a moml based composite actor.
>Kepler-dev mailing list
>Kepler-dev at ecoinformatics.org
Edward A. Lee
Professor, Chair of the EE Division, Associate Chair of EECS
231 Cory Hall, UC Berkeley, Berkeley, CA 94720
phone: 510-642-0253 or 510-642-0455, fax: 510-642-2845
eal at eecs.Berkeley.EDU, http://ptolemy.eecs.berkeley.edu/~eal
More information about the Kepler-dev