[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]

COPY / PROXY and the Translator

Non-PROXY messages in a proxified class should also
	 not be DEFERRED, since the stubble generated Proxy subclass will have
	 to be a concrete class (XLint doesn't need to check for this, the
	 compiler will).

Presumably member functions in the PROXY forward the message over the
wire.  This is completely automatically generated and shouldn't care
whether a body for the real object was defined.  Concrete subclasses
could then be defined which could be exported to another machine only
as the parent type.

   I agree.  If I understand stubble & formic correctly, there is no
   reason for all the copy variables to be gathered together in one COPY
   section instead of having several (Mr Hill?  Roland?  Do I have this

I hope this works because the easy solution generates a COPY
declaration for each variable.