ik wrote:
Hi,
I'm trying to translate the following error message:
parser_e_ill_msg_param=03144_E_Message handlers can take only one call
by ref. parameter
% A method declared with the \var{message}-directive as message handler
% can take only one parameter which must be declared as call by ref
Hi,
I'm trying to translate the following error message:
parser_e_ill_msg_param=03144_E_Message handlers can take only one call
by ref. parameter
% A method declared with the \var{message}-directive as message handler
% can take only one parameter which must be declared as call by reference
% Pa
On Fri, 30 Jun 2006, Sergei Gorelkin wrote:
> On Friday, June 30, 2006, 6:46:48 PM, Michael Van Canneyt wrote:
>
> MVC> There is a difference for the implementor of streams:
> MVC> By keeping the method abstract, you FORCE the implementation of a method
> MVC> in a descendent.
>
> MVC> The com
On Friday, June 30, 2006, 6:46:48 PM, Michael Van Canneyt wrote:
MVC> There is a difference for the implementor of streams:
MVC> By keeping the method abstract, you FORCE the implementation of a method
MVC> in a descendent.
MVC> The compiler will warn you if you try to instantiate a class which h
On Fri, 30 Jun 2006, Sergei Gorelkin wrote:
Hello,
Currently, TStream.Read and TStream.Write methods are abstract.
This means that each and every descendant of TStream must override these
methods with their implementation.
FCL has many read-only or write-only TStream descendants, which
overr
Hello,
Currently, TStream.Read and TStream.Write methods are abstract.
This means that each and every descendant of TStream must override these
methods with their implementation.
FCL has many read-only or write-only TStream descendants, which
override Read or Write methods just to indicate that m
