New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hpx simple component docs #752
Comments
Yes, but is this the simplest way of using components? In the action invocations it sounds like one just has to register a member function, while the allocator consists of server, stubs and client. |
The docs need updating here and there, but essentially that's it, yes. Note that the stub/client classes are just thin wrappers around a
|
ok i got a trivial example running, based on the quickstart/component_in_executable.cpp example. In your code above I think new_ returns a future, so it should be
and then
It took me way more time than it should, the docs in http://stellar.cct.lsu.edu/files/hpx_master/docs/html/hpx/manual/applying_actions/action_type_definition.html are very misleading, e.g. why is there the macro HPX_COMPONENT_EXPORT that never appears in the examples? Then it even says a note on the second argument for the HPX_REGISTER_ACTION_DECLARATION, but the line below doesn't have a second argument? |
Yes, I added the Could you provide a patch for the docs based on your experience? You will know best what you missed and what's wrong there. |
Can this be closed now? |
add a descriptive example on how to use a simple_component. For example there: http://stellar.cct.lsu.edu/files/hpx_master/docs/html/hpx/manual/applying_actions/action_invocation/apply.html describe how to get the global address of an instance, how to create such an instance in the first place. One is completely lost at that point. A short walk-through for simple components (maybe also managed components) would be very helpful in the docs.
The text was updated successfully, but these errors were encountered: