abstract ;;Quote: the process paradigm: ports carry interface type information, no inheritance, code associated with value of a port instead of type
|
abstract+;;Quote: both object-oriented and process paradigms based on message passing with clear separation between interface and implementation
|
89 ;;Quote: message passing emphasizes remoteness of object and caller's lack of knowledge
|
89+;;Quote: a procedure call can be viewed as an exchange of messages
|
90 ;;Quote: process paradigm corresponds to active entities in a physical system interacting through interfaces
|
90 ;;Quote: in process paradigm, a process calls another with an output port and a parameter list; message is passed from output port to an input port
|
90 ;;Quote: in process paradigm there is no global state or global time due to concurrent activity
|
90 ;;Quote: a process can communicate with another only after receiving a connection to an input port
|
93 ;;Quote: in process paradigm, the type of an interface is independent of its implementation
|
95 ;;Quote: can cast a variable to type Anytype; communicate it; then recast it to its original type for use
|
95 ;;Quote: object-oriented emphasizes global structure while process paradigm insists that all data is local
|
95 ;;Quote: in the process paradigm no system-wide knowledge, no superuser, no centralized management; everything is distributed
|
95 ;;Quote: object-oriented paradigm best for writing systems that can be understood by one person
|
95 ;;Quote: process paradigm best for very large systems since users never need to see, and can not see, the system as a whole
|