... | @@ -60,5 +60,4 @@ public: |
... | @@ -60,5 +60,4 @@ public: |
|
|
|
|
|
```
|
|
```
|
|
|
|
|
|
The two definitions are equivalent, but the second one give the possibility to analyse the members of the basic data. This can be useful when the memory representation (see below) can depend from the basic object. Other useful information for example for IO can be appended to the basic object, see
|
|
The two definitions are equivalent, but the second one give the possibility to analyse/parse the members of the basic data. This can be useful in several situation, when the memory representation ([Mappings](Memory-mappings)) depend from the basic object, or for IO to produce output that require to go through each element of the structure to produce a nice output, or VCluster to check that the data structure you are sending contain no pointers. In any case all the structures implemented in OpenFPM_data must work at least with the OpenFPM data structure format. In case you are going to implementing a new structure inside OpenFPM_data, consider to use already implemented structure like vector or grid that already implements the capabilities that we are going to present in the following sections. |
|
OpenFPM_IO. In any case all the structures implemented in OpenFPM_data must work with both format. In case of implementing a new structure inside OpenFPM_data, consider to use already implemented structure like vector or grid that already implements the capabilities that we are going to present in the following sections. It is allowed to treat the two form in the same way but strongly discouraged, because iy will be an extremely limiting factor. |
|
\ No newline at end of file |
|
\ No newline at end of file |
|
|