next up previous contents
Next: Library interface Up: Writing a distribution library Previous: Writing a distribution library   Contents


Configuration file

for each distributed argument, a configuration file is associated. This file fixes the data type on the parallel invocation and the descriptor type. Then it fixes how the PaCO++ layer is giving the pointer of the distributed data to the library.

There is four fields into this configuration file :

@@ARG_TYPE@@
In this version, each distributed is a sequence of sequence of a type. You define the type with this macro. You have two choices :

ARG_TYPE
In this case, the type is the type define in the method. PaCO++ gives to the library the pointer of the data without any process. Example : in my_type dis_data $\Rightarrow$ typedef sequence$\langle$sequence$\langle$my_type$\rangle$$\rangle$ real_dis_data;

ARG_TYPE_SEQ_
In this case, the data is a sequence. PaCO++ layer is going to use the get_buffer method to give a pointer to the library. PaCO++ is also going to use the data constructor to avoid copies. Example : typedef sequence$\langle$long$\rangle$ my_type; $\Rightarrow$ typedef sequence$\langle$sequence$\langle$long$\rangle$$\rangle$ real_dis_data;

@@DESCR@@
With this macro, you define the type of decriptor associated with the distributed data. If DESCR==corba, the type is a basic corba type. If the type is not a corba basic type, you can specify a file where the description type is defined. The PaCO++ compiler try to read this file on the root_paco++/DistributionLibraries/Types directory.

@@DESCR_IDL@@
This is the type name of the descriptor. Example : long or my_descr_type.

@@DESCR_REAL@@
This is the real type name in the target language. Currently, only C++ is supported. Example : CORBA::Long or my_descr_type.


next up previous contents
Next: Library interface Up: Writing a distribution library Previous: Writing a distribution library   Contents
2013-04-10