By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,194 Members | 810 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,194 IT Pros & Developers. It's quick & easy.

Compiler io problem!

P: n/a
I'm using the Borland 5.5 Standard Edition compiler and recently started having
an io problem. When I Run my applications, after compiling and linking, there
is no output to the output window! it's as though the output is being
redirected elsewhere. I've tried removing and re-installing Borland 5.5 several
times but the problem persists. I've been using this Borland package for well
over a year with no problems and feel safe to rule out the Borland package as
the problem. Perhaps some setting on my system has changed, I'm using windows
98.

I contacted Borland about the problem and am still awaiting a reply. In the
meantime I'm hoping some of you Pros out there might have some ideas to help me
resolve the problem.

JB
Jul 19 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
jbruno4000 wrote:
I'm using the Borland 5.5 Standard Edition compiler and recently started having
an io problem. When I Run my applications, after compiling and linking, there
is no output to the output window! it's as though the output is being
redirected elsewhere. I've tried removing and re-installing Borland 5.5 several
times but the problem persists. I've been using this Borland package for well
over a year with no problems and feel safe to rule out the Borland package as
the problem. Perhaps some setting on my system has changed, I'm using windows
98.

I contacted Borland about the problem and am still awaiting a reply. In the
meantime I'm hoping some of you Pros out there might have some ideas to help me
resolve the problem.

JB


The easy way for us to help you resolve your issue is for you to post
the smallest compilable program that demonstrates the issue.
Tell us the expected behavior and the actual behavior.

The problem is that I/O is quite vague. Are you using the correct
functions for outputting to a window? Are you writing to the correct
window? Is this a console window? Are you mixing "C" style streams
with C++ streams? Did your program execute the code to output to
the window? Was there any data to be output? Did the output function
return any error?

Many of the above questions could be resolved by posting, not
attaching, code. Just paste into the post, don't retype.

Reread your post and see if there is enough information in it for
you to figure out what is going on.

--
Thomas Matthews

C++ newsgroup welcome message:
http://www.slack.net/~shiva/welcome.txt
C++ Faq: http://www.parashift.com/c++-faq-lite
C Faq: http://www.eskimo.com/~scs/c-faq/top.html
alt.comp.lang.learn.c-c++ faq:
http://www.raos.demon.uk/acllc-c++/faq.html
Other sites:
http://www.josuttis.com -- C++ STL Library book

Jul 19 '05 #2

P: n/a
to test the compiler I entered some simple code. i.e.

#include <iostream>

using namespace std;

int main()
{
cout << "Hello everybody!";

return 0;
}

Before the problem began this program would execute correctly by displaying the
message "Hello everybody" to the output screen.
Jul 19 '05 #3

P: n/a
jbruno4000 wrote:

cout << "Hello everybody!";


It might not matter, but change that to:

cout << "Hello everybody!" << endl;

(You might need to #include <ostream> for that to compile)

Neither C nor C++ makes any promises about what happens when text output
isn't terminated by a newline. endl puts in a newline and will also
flush the output, which sometimes makes a difference.

--

Pete Becker
Dinkumware, Ltd. (http://www.dinkumware.com)
Jul 19 '05 #4

P: n/a

From your response I can tell I'm not comminicating the problem effectively.
This is probably not the best place to address this sort of problem, too many
unknowns. I think I'm just going to have to restore my system as much as I
dread it!

Thanks anyway!
Jul 19 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.