ILS_GLOBAL_FUNCTION
 
ILS_GLOBAL_FUNCTION
Category 
Dynamic view-related macros
Description 
These macros declare global functions as being accessible at runtime, so that they can be used in dynamic view type specifications.
They MUST NOT be enclosed between the following pairs of macros:
*ILS_OBJECT_BEGIN/ILS_OBJECT_END
*ILS_ENTITY_BEGIN/ILS_ENTITY_END
*ILS_MVVIEW_BEGIN/ILS_MVVIEW_END
Header File 
<ilserver/rtmodel.h>
Synopsis 
ILS_GLOBAL_FUNCTION0(resType,funNm)
ILS_GLOBAL_FUNCTION1(resType,funNm,param1Type)
ILS_GLOBAL_FUNCTION2(resType,funNm,param1Type,param2Type)
ILS_GLOBAL_FUNCTION3(resType,funNm,param1Type,param2Type,
param3Type)
ILS_GLOBAL_FUNCTION4(resType,funNm,param1Type,
param2Type,param3Type,param4Type)
ILS_GLOBAL_FUNCTION5(resType,funNm,param1Type,
param2Type,param3Type,param4Type,param5Type)
ILS_GLOBAL_FUNCTION6(resType,funNm,param1Type,param2Type,
param3Type,param4Type,param5Type,param6Type)
Arguments 
These macros take the following arguments, in this order:
*the type of the value returned by the function,
*the function name
*the types of the function parameters.
All the global runtime functions must have a unique name. The result and the parameters of a global function can be of the following types:
*char
*char*
*IlsString
*IlsBoolean
*short
*int
*long
*float
*double
*any type that derives from IlsMvUserType.
When a runtime-accessible global function is called from a component, the result is not sent back to this component, because the callback mechanism is completely asynchronous. However, to allow for the requirements of type macro expansion, such a function cannot have a result of type void.
See Also 
ILS_ENTITY_BEGIN/ILS_ENTITY_END, ILS_MVVIEW_BEGIN/ILS_MVVIEW_END, ILS_OBJECT_BEGIN/ILS_OBJECT_END

Version 5.8
Copyright © 2014, Rogue Wave Software, Inc. All Rights Reserved.