endwin() doesn't exit (obviously) nor does it handle STDOUT/STDERR/STDIN data. Your printed statements are stored by the shell until it is able to print them, namely when your program "let's go" of the terminal. If you redirect STDOUT to a file, you'd see that it appears immediately. It would be best if you could use the Curses calls instead of printing, since that is the point of Curses, but if you decide that you can't do that, try a wrefresh() after the print output AND unbuffer STDOUT. It's usually best to avoid endwin() since it means you wish to leave the pretty Curses environment. I have never found the need to do that- perhaps if you provide an example of why you'd need to do this....

If you need printf capability, use printw(). As always, hit your local docs- of which, currently, the C versions are far more complete.

AgentM Systems nor Nasca Enterprises nor Bone::Easy nor Macperl is responsible for the comments made by AgentM. Remember, you can build any logical system with NOR.