This is like MPI_Bcast. More...
#include "Tulip/Messaging.h"#include "Domain/Loc.h"#include "Tiny/Vector.h"#include "Functions/ComponentAccess.h"
Include dependency graph for RemoteProxy.h:
This graph shows which files directly or indirectly include this file:
Classes | |
| class | RemoteProxy< T > |
| This class is the return type of the remote brick engine operator(). More... | |
Functions | |
| template<class T , class S > | |
| T | operator* (const RemoteProxy< T > &t, const S &s) |
| Some mathematical operations. | |
Detailed Description
This is like MPI_Bcast.
It moves a value from one context to all others. Special about this is that assigns to a RemoteProxy object on the owning context is performed to the underlying data, while on the remote contexts it is just done to the proxy object.
Function Documentation
template<class T , class S >
| T operator* | ( | const RemoteProxy< T > & | t, |
| const S & | s | ||
| ) | [inline] |
Some mathematical operations.
These probably need to be improved to promote the types.
References RemoteProxy< T >::value().
