Skip to content
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::cout output does not appear on screen #851

Closed
eschnett opened this issue Sep 15, 2013 · 3 comments
Closed

hpx::cout output does not appear on screen #851

eschnett opened this issue Sep 15, 2013 · 3 comments
Assignees
Milestone

Comments

@eschnett
Copy link
Contributor

After replacing std::cout with hpx::cout, and using

#include <hpx/include/iostreams.hpp>

no output is shown on the screen. For example, the line

 hpx::cout << "Done.\n";

produces no output.

Am I doing something wrong? Do I need to add "<< hpx::flush" to the cout line? (Shouldn't there be an implied flush?)

Why does the include file path have "include" in it? Am I using the right include path?

Is there documentation somewhere that describes all HPX functions, and which include files one needs for them? I'm having a hard time finding out include paths and namespace prefixes (such as e.g. hpx::threads::thread_id_type, where hpx::thread_id_type doesn't work).

@hkaiser
Copy link
Member

hkaiser commented Sep 15, 2013

We have some documentation of the API, but by far not all is described yet. Your best bet is to start with the index: http://stellar.cct.lsu.edu/files/hpx_0.9.6/html/index/s05.html

@hkaiser
Copy link
Member

hkaiser commented Sep 15, 2013

Am I doing something wrong? Do I need to add "<< hpx::flush" to the cout line? (Shouldn't there be an implied flush?)

Yes, you need to use hpx::flush in order to send the buffers to the console. There should be an implicit flush at program termination. I added this as a feature request to #190.

Why does the include file path have "include" in it? Am I using the right include path?

There is no particular reason, it is a convention we adopted from other libraries we wrote in the past where foo/include holds forwarding headers to the actual library headers.

@ghost ghost assigned hkaiser Sep 15, 2013
@hkaiser
Copy link
Member

hkaiser commented Sep 15, 2013

I'll close this as a duplicate of #190

@hkaiser hkaiser closed this as completed Sep 15, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants