Re: [Dev-C++] classes and references

[<cg...@wo...>]

OROSZI Bal=E1zs wrote:

> Ioannis Vranos wrote:
>
>> But he explicitly mentions that the 3 first chapters are a quick tour=20
>> of the
>> language and he explicitly mentions that everything will become clear=20
>> later.
>> The learning process begins from chapter 4.
>
>
> For example: templates are first *used* in the 3rd chapter
> (___*****and from then continuously*****___, i.e. in the 4th and 5th=20
> and so on) and described in the 12th...
> This caused me a lot of headache, he used it a lot of times, and I had=20
> absolutely no idea what hell is vector<xxx> for example...=20

How in the hell can anyone understand the examples given for features if=20
the example program is full of unexplained features??. Well, one can=20
understand some of such kind of things in the very beginning of the=20
book. Well, I hope it has at least the currently feature which is being=20
explained highlighted. But it's like say to kids," hey: we'll start to=20
learn multiplication... let's work with Schr=F6dinger formulae."
Certainly sometimes it can be needed or justified, but I doubt very much=20
using templates or vectors is absolutely needed before explaining them.=20
Then or you explain them at begin (at least the minimum you use and=20
then, the 12th chapter in detail or you explain it along the book, the=20
features as they are being used in the next chapters and then at the end=20
a chapter explaining all about them a a reminder) or you shall try to=20
avoid examples which need them.

And vectors have nothing to do with templates, although vectors are=20
implemented as templates. Vectors are a kind of "array" (forgive my not=20
technical language) which is safer and more "complex" but also very=20
powerful, mainly in the dinamic memory management.

>
>
>> I do not like it too, but it is what it takes to become a good=20
>> programmer.
>> That said you do  not need to know all the features provided by C++=20
>> to do
>> programs, but it takes years to learn it all (assuming you also have=20
>> other
>> things to do daily).
>
>
> Well, that is called _experience_. I think it is way different from=20
> knowing, what a code part from another project does...

Yeah, the minimum is explaining what that code which uses features which=20
are not been explained does, and the one explained too.
Experience, or code, code and more code. But for having enough for that=20
experience being useful I lasted six months.(I had still some stupid=20
errors, but they were corrected more or less easily. Now, after a year=20
and a half I can write program without errors (not big programs) and=20
they do what I want. However, I don't consider me a guru yet, I'm still=20
far, but not too much).

>
>> I shall say that I will have a good knowledge of C++ after I have=20
>> finished
>> the book inclduing the appendices. :)
>
>
> No. Then you will have absolute knowledge. A C++ guru in other words. :=
)=20

It depends on the level of the book. But for being a guru you need end,=20
including appendices, some (many) books, or many, many * 5 practicing.

>
>
>> Well it is aimed towards itermediate programmers. However my belief=20
>> is that
>> every programmmer of C++ should have read this book.
>
>
> Yes, *should have*...=20

Which book? :-D  Yeah TC++PLSE.

>
>
> --=20
> Greets,
>   Bal=E1zs
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>