🚀 go-pugleaf

In article <69283@cup.portal.com>, lozinski@cup.portal.com (Christopher A Lozinski) writes:
|> PRODUCT ANNOUNCEMENT
|> 
|>      The Smalltalk Interface to Objective-C makes Objective-C
|> objects look like Smalltalk objects.  The interface is based on the
|> simple concept that every remote Objective-C class and instance can
|> be represented by a local Smalltalk proxy object.  Messages sent to a
|> local Smalltalk proxy object are transparently forwarded to the
|> actual Objective-C object it represents, and the results are returned
|> as Smalltalk objects.  To the Smalltalk developer, there are just
|> Smalltalk messages being sent to Smalltalk objects.  To the
|> Objective-C developer, there are just Objective-C messages being sent
|> to Objective-C objects.  The net result is that the two languages are
|> very smoothly integrated.  
|> 

Is communication one-way or two-way?  For example, can a Smalltalk
method call an Objective-C method which in turn calls a Smalltalk
method?


James W. Howe                  internet: jwh@citi.umich.edu
University of Michigan             uucp: uunet!mailrus!citi.umich.edu!jwh
Ann Arbor, MI   48103-4943