"Accelerate d C++" beginner question.

[TonyJeffs]

Great book - I like the way that unlike other books, AC++ explains as
much as possible about every piece of code discussed, so I'm not left
thinking, "well...OK. .. I get line 12, but I wonder what the rest of
it means...".

Still, I have some questions, that are frustrating me:-
Grateful for any comments.

1. What is the difference between
#include <iostream> // (or any include file) which is used in this
book, and
#include <iostream.h> // which is used in other books I've looked at.

2. Does the absence of the '.h' have something to do with the need
for std:: before cout ?

3. std, the book esplains, is a namesace. But what is a namespace,
particularly in this case?. Is it something I can open and look at in
Notepad?

............... ............... .......
I'm up to chapter 4, and relativaly comfortable with it, but these
early questions are still nagging me.

Thanks

[Pelle Beckman]

TonyJeffs skrev:

Great book - I like the way that unlike other books, AC++ explains as
much as possible about every piece of code discussed, so I'm not left
thinking, "well...OK. .. I get line 12, but I wonder what the rest of
it means...".

Still, I have some questions, that are frustrating me:-
Grateful for any comments.

1. What is the difference between
#include <iostream> // (or any include file) which is used in this
book, and
#include <iostream.h> // which is used in other books I've looked at. #include <iostream> is the suggested way of including files
in c++ (at least for standard libraries)
#include <iostream.h> is just about the same, except most
compilers will give you a warning telling you its deprecated.
When writing your own header files - select what suits you the best.
Personally, I like .h or .hpp

2. Does the absence of the '.h' have something to do with the need
for std:: before cout ?
No.
3. std, the book esplains, is a namesace. But what is a namespace,
particularly in this case?. Is it something I can open and look at in
Notepad?

A namespace is a concept of grouping things - like functions, classes
and constants - that belong together.
Using namespaces makes your code more readable and more easily
maintained.
The standard libraries, such as iostream, use a namespace called
std - that's why you see things like 'std::cout << "blah" << std::endl;'
or 'using namespace std;'

Google it.

-- Pelle

[Sharad Kala]

"TonyJeffs" <to*******@aol. com> wrote in message

Great book - I like the way that unlike other books, AC++ explains as
much as possible about every piece of code discussed, so I'm not left
I haven't read anyone saying otherwise about the book :-)
thinking, "well...OK. .. I get line 12, but I wonder what the rest of
it means...".

Still, I have some questions, that are frustrating me:-
Grateful for any comments.

1. What is the difference between
#include <iostream> // (or any include file) which is used in this
book, and
#include <iostream.h> // which is used in other books I've looked at.
The other books you have looked at are outdated. Standard headers are
extensionless.

2. Does the absence of the '.h' have something to do with the need
for std:: before cout ?
Yes, everything inside standard headers is wrapped inside std namespace. So
cout needs to be addressed as std::cout.
3. std, the book esplains, is a namesace. But what is a namespace,
particularly in this case?. Is it something I can open and look at in
Notepad?

What have namespaces to do with Notepad ?? Namespaces allow us to group a
set of global classes, objects and/or functions under a name. This helps in
avoiding name conflicts, and redefinition errors.

namespace a {
int i; // OK
}

namespace b {
int i; // OK
}

Sharad

[Sharad Kala]

"Pelle Beckman" <he******@chell o.se> wrote in message

1. What is the difference between
#include <iostream> // (or any include file) which is used in this
book, and
#include <iostream.h> // which is used in other books I've looked at. #include <iostream> is the suggested way of including files

Not suggested, but correct way of including files in ISO C++.
in c++ (at least for standard libraries)
#include <iostream.h> is just about the same, except most
compilers will give you a warning telling you its deprecated.
When writing your own header files - select what suits you the best.
Personally, I like .h or .hpp

2. Does the absence of the '.h' have something to do with the need
for std:: before cout ?

No.

Why ?

3. std, the book esplains, is a namesace. But what is a namespace,
particularly in this case?. Is it something I can open and look at in
Notepad?

A namespace is a concept of grouping things - like functions, classes
and constants - that belong together.
Using namespaces makes your code more readable and more easily
maintained.

Is that the only goal of namespaces ?

Sharad

[Andrew Koenig]

"TonyJeffs" <to*******@aol. com> wrote in message
news:8e******** *************** ***@posting.goo gle.com...

1. What is the difference between
#include <iostream> // (or any include file) which is used in this
book, and
#include <iostream.h> // which is used in other books I've looked at.
<iostream.h> is not part of standard C++, although many implementations
include it for compatibility with earlier usage.
2. Does the absence of the '.h' have something to do with the need
for std:: before cout ?
Yes.
3. std, the book esplains, is a namesace. But what is a namespace,
particularly in this case?. Is it something I can open and look at in
Notepad?

A namespace is something that is part of the C++ language. It is not a data
structure that you can access directly. A namespace has a name and contains
a (possibly empty) collection of names. When you want to use one of the
names that a namespace contains, you can refer to it as x::y, where x is the
name of the namespace and y is the name that it contains.

So when you say

#include <vector>

the compiler puts the name "vector" into the namespace named "std", after
which you can refer to std::vector. Alternatively, by saying "using
std::vector;" you can cause the name "vector" to be brought into the global
namespace, after which you can refer to vector without the "std::" in front
of it.

[Ioannis Vranos]

TonyJeffs wrote:

Great book - I like the way that unlike other books, AC++ explains as
much as possible about every piece of code discussed, so I'm not left
thinking, "well...OK. .. I get line 12, but I wonder what the rest of
it means...".

Still, I have some questions, that are frustrating me:-
Grateful for any comments.

1. What is the difference between
#include <iostream> // (or any include file) which is used in this

This is valid C++.

book, and
#include <iostream.h> // which is used in other books I've looked at.

This is not valid C++. It was used before the final C++ standard.
2. Does the absence of the '.h' have something to do with the need
for std:: before cout ?
No.
3. std, the book esplains, is a namesace. But what is a namespace,
particularly in this case?. Is it something I can open and look at in
Notepad?

We can say that namespace is a scope for grouping facilities.

--
Ioannis Vranos

http://www23.brinkster.com/noicys

[Alf P. Steinbach]

* Pelle Beckman:

TonyJeffs skrev:

Great book - I like the way that unlike other books, AC++ explains as
much as possible about every piece of code discussed, so I'm not left
thinking, "well...OK. .. I get line 12, but I wonder what the rest of
it means...".

Still, I have some questions, that are frustrating me:-
Grateful for any comments.

1. What is the difference between
#include <iostream> // (or any include file) which is used in this
book, and
#include <iostream.h> // which is used in other books I've looked at. #include <iostream> is the suggested way of including files
in c++ (at least for standard libraries)

No suggestion.

<iostream> is a standard header.

<iostream.h> is not, and is only available with certain compilers.

#include <iostream.h> is just about the same, except most
compilers will give you a warning telling you its deprecated.

_No_ compiler will tell you that.

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[tony_jeffs]

Thanks for all the advice. As well as helping me know what's going on,
any interaction on the topic will be a big help in keeping me going
and on track!

My next Question (sec 4.1.2 in case anyone wants to look at the
book):

const vector<double>& hw =homework)

I follow that hw is a synonym for homework.
But it seems to me that '&' does not mean 'the address of' in this
case. It means something a bit different. Am I correct? What phrase
could I use to explain the &?
Does this & mean 'by reference'?

(You'll see my brain's a bit cluttered with things I've half read and
half understood in the past!!)

Thanks again,

Tony

[Peter Kragh]

tony_jeffs wrote:

My next Question (sec 4.1.2 in case anyone wants to look at the
book):

const vector<double>& hw =homework)

I follow that hw is a synonym for homework.
But it seems to me that '&' does not mean 'the address of' in this
case. It means something a bit different. Am I correct? What phrase
could I use to explain the &?
Does this & mean 'by reference'?

Not quite. In this context & means that hw is a reference. Look up
references in your book.

To quote another great C++ book (C++ Primer, Lippman & Lajoie): "A
reference, sometimes referred to as an alias, serves as an alternative
name for an object. A reference allows for the indirect manipulation of
an object in a manner similar to the use of a pointer but without
requiring use of pointer syntax".

But what does that mean in real life? Lets look at an example:

Using a pointer:

void GetName(std::st ring* name)
{
// Check if name is valid
if(!name)
{
throw std::runtime_er ror("Invalid name pointer");
}

// Do something to get a name
...

*name = "something" ;
}

Using a reference:

void GetName(std::st ring& name)
{
// Do something to get a name
...

name = "something" ;
}

By using a reference parameter instead of a pointer parameter, the
compiler will make sure that you get a valid object you can use
(although there are pitfalls!). If you use a pointer you need to do the
checking by yourself.

There are other ways of using a reference type. Compare these two functions:

void OutputName(std: :string name)
{
....
}

void OutputName(cons t std::string& name)
{
....
}

What's the difference? Calling the first function will pass a copy of
the name (which of course means that a copy will be made). Calling the
second function will only pass a reference to the name (much cheaper,
especially when dealing with long strings, vectors, etc.).

HTH.

--
Peter

[enki]

Are you realy the guy who wrote those C++ books?
How is Bjarne?