«

I am trying to build a Hello World program in C++. I am using the c++ or
g++ complier in cygwin. My mangled code looks like this,

#include <iostream>

int main ()
{
cout << "Hello World";
return;
}

It looks like my example but it isn't working.

the compiler for g++ tells me the following:

hellotest.cpp: In function `int main()':
hellotest.cpp:5: error: `cout' undeclared (first use this function)
hellotest.cpp:5: error: (Each undeclared identifier is reported only once
for each function it appears in.)
hellotest.cpp:6: error: return-statement with no value, in function
returning 'int'

When I run it with an older complier Borland 4.5 it tells me that it can't
read the input file helloworld.rc.

What am I doing wrong?

knilges wrote:
> I am trying to build a Hello World program in C++. I am using the c++ or
> g++ complier in cygwin. My mangled code looks like this,
>
> #include <iostream>
>
> int main ()
> {
> cout << "Hello World";
> return;
> }

int main()
{
std::cout << "Hello World" << std::endl;
return 0;
}
>
> It looks like my example but it isn't working.
>
> the compiler for g++ tells me the following:
>
> hellotest.cpp: In function `int main()':
> hellotest.cpp:5: error: `cout' undeclared (first use this function)
> hellotest.cpp:5: error: (Each undeclared identifier is reported only once
> for each function it appears in.)
> hellotest.cpp:6: error: return-statement with no value, in function
> returning 'int'
>
> When I run it with an older complier Borland 4.5 it tells me that it can't
> read the input file helloworld.rc.

That is some sort of compiler dependent file.
>
> What am I doing wrong?

knilges wrote:
> I am trying to build a Hello World program in C++. I am using the c++ or
> g++ complier in cygwin. My mangled code looks like this,
>
> #include <iostream>
>
> int main ()
> {
> cout << "Hello World";

replace the above line with:

std::cout << "Hello World";

and your program will compile fine.

> return;

Delete the above line entirely, or replace it with:

return 0;

> }
>

Best regards,

Tom

wrote:
> knilges wrote:
>> I am trying to build a Hello World program in C++. I am using the c++ or
>> g++ complier in cygwin. My mangled code looks like this,
>>
>> #include <iostream>
>>
>> int main ()
>> {
>> cout << "Hello World";
>> return;
>> }
>
> int main()
> {
> std::cout << "Hello World" << std::endl;
> return 0;
> }

Or just leave out the return - a main() with no return is assumed to
return EXIT_SUCCESS.

--
Mike Smith

On 18 Jan 2006 07:57:58 -0800 in comp.lang.c++,
wrote,
> std::cout << "Hello World" << std::endl;

endl is uncalled for there. Please don't teach bad habits.
If you want to add a newline, it should be:

std::cout << "Hello World\n";

David Harmon wrote:
> On 18 Jan 2006 07:57:58 -0800 in comp.lang.c++,
> wrote,
> > std::cout << "Hello World" << std::endl;
>
> endl is uncalled for there. Please don't teach bad habits.
> If you want to add a newline, it should be:
>
> std::cout << "Hello World\n";

Since std::cout may very well be buffered it is actually prudent to
pass std::endl instead of '\n'. In this *particular* case, since the
program exits immediately following the operation it is "unneccisary"
but it is a GOOD habit to get into since in anything more complex than
a hello world program is going to do more and you should flush your
outputs when you want them to be sent.

So, to each his own. I'll answer questions the way I see fit and
people can learn, or not, what they want.

Thanks anyway.

<> wrote in message
news: oups.com...
>
> David Harmon wrote:
>> On 18 Jan 2006 07:57:58 -0800 in comp.lang.c++,
>> wrote,
>> > std::cout << "Hello World" << std::endl;
>>
>> endl is uncalled for there. Please don't teach bad habits.
>> If you want to add a newline, it should be:
>>
>> std::cout << "Hello World\n";
>
> Since std::cout may very well be buffered it is actually prudent to
> pass std::endl instead of '\n'. In this *particular* case, since the
> program exits immediately following the operation it is "unneccisary"
> but it is a GOOD habit

IMO a 'good' habit would be something that is
always 'good' in general (e.g. use consistent
indentation style). But imo 'proper' use of
'endl' depends much upon context. Because of
what it does, using it needlessly can unnecessarily
degrade performance. (i/o is typically the slowest
part of a system -- that's why buffering was invented).

> to get into since in anything more complex than
> a hello world program is going to do more and you should flush your
> outputs when you want them to be sent.

But it's often the case that 'visible' output is not needed
at every occurence of '\n'.


> So, to each his own. I'll answer questions the way I see fit and
> people can learn, or not, what they want.

And others will insert their opinions as they see fit.

FWIW I've still never had the need to use 'endl' with
output streams.

-Mike

Mike Wahler wrote:
> <> wrote in message
> news: oups.com...
> >
> > David Harmon wrote:
> >> On 18 Jan 2006 07:57:58 -0800 in comp.lang.c++,
> >> wrote,
> >> > std::cout << "Hello World" << std::endl;
> >>
> >> endl is uncalled for there. Please don't teach bad habits.

> > So, to each his own. I'll answer questions the way I see fit and
> > people can learn, or not, what they want.
>
> And others will insert their opinions as they see fit.

Well it seems some people feel I need permission to do so.

Mike Wahler wrote:
> <> wrote in message
> news: oups.com...
> >
> > David Harmon wrote:
> >> On 18 Jan 2006 07:57:58 -0800 in comp.lang.c++,
> >> wrote,
> >> > std::cout << "Hello World" << std::endl;
> >>
> >> endl is uncalled for there. Please don't teach bad habits.

> > So, to each his own. I'll answer questions the way I see fit and
> > people can learn, or not, what they want.
>
> And others will insert their opinions as they see fit.

Well it seems some people feel I need permission to do so.

<> wrote in message
news: oups.com...
>
> Mike Wahler wrote:
>> <> wrote in message
>> news: oups.com...
>> >
>> > David Harmon wrote:
>> >> On 18 Jan 2006 07:57:58 -0800 in comp.lang.c++,
>> >> wrote,
>> >> > std::cout << "Hello World" << std::endl;
>> >>
>> >> endl is uncalled for there. Please don't teach bad habits.
>
>> > So, to each his own. I'll answer questions the way I see fit and
>> > people can learn, or not, what they want.
>>
>> And others will insert their opinions as they see fit.
>
> Well it seems some people feel I need permission to do so.

Really? I haven't seen any indication of that. If someone
responds to your post with e.g. "don't say that", that simply
means they disagree, not that they're demanding you ask permission
to say it. (Civilly expressed) disagreements often lead to
useful discussion. Discussion sheds light on both sides of an
issue, and allows observers to draw their own conclusions.
I think that is especially useful for the novice.

-Mike