Learning C++

[Jeremy Cowles]

I am reading the book, "Core C++", this is 90% focused on the language, not
the STL. What book should I get next, something on the STL or an
OS-specific book (such as the win32 api), or something else?

I feel like I am not retaining enough of what I am reading. This might be
because I'm not writing much code - all I can write is console apps that
don't actually do anything since I don't know how to use the STL. Any
suggestions?

Thanks,
Jeremy

 

[David Rasmussen]

I am reading the book, "Core C++", this is 90% focused on the language, not
the STL. What book should I get next, something on the STL or an
OS-specific book (such as the win32 api), or something else?

I feel like I am not retaining enough of what I am reading. This might be
because I'm not writing much code - all I can write is console apps that
don't actually do anything since I don't know how to use the STL. Any
suggestions?

"Accelerated C++" all the way.

http://www.acceleratedcpp.com/

http://www.amazon.com/exec/obidos/t...1/ref=cm_lm_asin/104-7524768-9443969?v=glance

/David

 

[Kamil Burzynski]

I am reading the book, "Core C++", this is 90% focused on the language, not
the STL. What book should I get next, something on the STL or an
OS-specific book (such as the win32 api), or something else?

I feel like I am not retaining enough of what I am reading. This might be
because I'm not writing much code - all I can write is console apps that
don't actually do anything since I don't know how to use the STL. Any
suggestions?

IMHO what you need most is experience. Write as much as you can. Soon
you will discover which direction you should improve.

Of course reading books in the same time may only help, especially if
you want to learn STL (btw. for beginner writing C++ programs without
STL is acceptable, especially if you know that STL exists and you should
use it ;P - this approach you will learn 'the other way' and after
switching to STL you'll see how it is better).

Regarding to books I would recommend Stroustrup book, and Josuttis' one
about Standard Library (sorry, but I don't remember exact english
titles).

 

[green earth]

(btw. for beginner writing C++ programs without

STL is acceptable, especially if you know that STL exists and you should
use it

also there is no reason why you _should_ use STL even if you're not a
beginner

 

[Jonathan Turkanis]

(btw. for beginner writing C++ programs without

also there is no reason why you _should_ use STL even if you're not a
beginner

Because implementing hand-rolled data structures and algorithms is
usually a watse of time when there are already general purpose
implementations available which are likely to be more efficient and
correct. (Note is said 'usually')

Implementing data structures and algorithms is a good exercise, but
when you actually need to use them, that's a different story.

Jonathan

 

[Phlip]

(btw. for beginner writing C++ programs without

also there is no reason why you _should_ use STL even if you're not a
beginner

There's no reason why you should use 'int', even if you're not a beginner.

 

[Fred H]

and Josuttis' one
about Standard Library (sorry, but I don't remember exact english
titles).

The C++ Standard Library - A Tutorial and Reference, Nikolai M. Josuttis.


--
Fred H

void FredH::Contact() {
TextToSpeach.say("frode at age dee dee dot en oh");
}

 

[Victor Bazarov]

The C++ Standard Library - A Tutorial and Reference, Nikolai M. Josuttis.

It's Nicolai. C, not K.

 

[NKOBAYE027]

there are manifold reasons to use the STL everything from portabilty and
compatibility with thrid party libraries to saving time by not trying to
reinvent the wheel (with the inevitable alignment problems you'll have in
your version) to better performaning and safer code...It's a fun exercise to
write your own deque or map, but generally, the real thing should be left to
those older and wiser and more versed/experienced than i am (and any newbie
for that matter). to better understand the STL just do your google thang )
you'll find scads of tutorials, faqs and foibles on the net to inform you.

good luck and have fun

regards,
Lup

 

[Jeremy Cowles]

Thanks.

 

[Attila Feher]

(btw. for beginner writing C++ programs without

also there is no reason why you _should_ use STL even if you're not a
beginner

There is no reason why you _should_ use C++ either. But if you want to
learn C++, you are better off using the Standard Library (note: not STL) and
only start rolling your own data structures if you must.

 

[Jeremy Cowles]

There is no reason why you _should_ use C++ either. But if you want to
learn C++, you are better off using the Standard Library (note: not STL)

Now I'm confused. What is the difference between the Standard Library and
STL?

 

[Kamil Burzynski]

Now I'm confused. What is the difference between the Standard Library and
STL?

Standard Template Library is a part of Standard Library. SL contains
other facilities than STL, too: streams, std::string and so on.

 

[Pete Becker]

Now I'm confused. What is the difference between the Standard Library and
STL?

The STL part of the Standard C++ Library is containers, iterators, and
algorithms.

 

[Jeremy Cowles]

Standard Template Library is a part of Standard Library. SL contains
other facilities than STL, too: streams, std::string and so on.

Ok I see, the STL is a subset of the Standard Library. Thanks.

 

[Jon Bell]

Ok I see, the STL is a subset of the Standard Library. Thanks.

Not quite. The STL (Standard Template Library) predates the C++ standard
(so it was "standard" only in the hopes of its authors). Most of the STL
became part of standard C++, but some if it didn't.