Elysian Shadows

Tell people to familiarize themselves with stl(standard template library) its a great place to start for c++.

Levio91 wrote:Tell people to familiarize themselves with stl(standard template library) its a great place to start for c++.

what?

avansc wrote:

Levio91 wrote:Tell people to familiarize themselves with stl(standard template library) its a great place to start for c++.

what?

I was laughing for 5 minutes xD

I imagined you saying that by animating your avatar picture in my head..

cypher1554R wrote:

avansc wrote:

Levio91 wrote:Tell people to familiarize themselves with stl(standard template library) its a great place to start for c++.

what?

I was laughing for 5 minutes xD

I imagined you saying that by animating your avatar picture in my head..

lolz

avansc wrote:what?

What do you mean, what? STL has a bunch of useful things that make your life easier, and professors tend to not cover it, and intro classes tend to not mention it at all.

MarauderIIC wrote:

avansc wrote:what?

What do you mean, what? STL has a bunch of useful things that make your life easier, and professors tend to not cover it, and intro classes tend to not mention it at all.

two reasons i say what for.

1. its not a good place to start for C++ (that was my main reason)
2. as a C programmer i tend to look down on certain STL things. if it was used responsibly it be fine, but people will just use it all the time even if they dont know the mechanics behind it. the name STL is a oxymoron, because its not standard. STL has numerous design issues that just make it unacceptable for for someone serious about their software to use. there are even things in the STL like copy_if that was just left out because of oversight()may have changed. its inefficient that you cant choose memory from the pools you want.

STL tries to do what java does. and i guess its fine, but its sub standard to me at least. and is not accepted in the industry.

there is nothing STL can do beter than what a decent coder can.

edit: i was in a foul mood last night so this is probably a hard evaluation. STL has its place. but i always recommend knowing how to do things yourself if need be.

In our project, we use STL extremely sparingly. It isn't something that a console developer should rely heavily on.

yeah... I guess if you're able to create your own data structures, you're able to control every property/attribute that they have, and your cutting away the extra 'fat' you would get with an STL object.

could be a valuable learning experience to create your own templates, rather than rely on what is commonly provided for you in any ANSI compliant/standardised compiler/IDE.

but hey, what do I know?

programmerinprogress wrote:yeah... I guess if you're able to create your own data structures, you're able to control every property/attribute that they have, and your cutting away the extra 'fat' you would get with an STL object.

could be a valuable learning experience to create your own templates, rather than rely on what is commonly provided for you in any ANSI compliant/standardised compiler/IDE.

but hey, what do I know?

stl is not standardized by everyone, if it was it would be alot safer/beter to use.

programmerinprogress wrote:could be a valuable learning experience to create your own templates, rather than rely on what is commonly provided for you in any ANSI compliant/standardised compiler/IDE.

Yeah, I agree. Actually, that's what my CPE212 class made you do, just because it was such a good exercise.

You learn not only templates, but data structures as well. I agree.

Honestly, I dislike using STL for many things...I tend to write my own custom classes for what-ever best suits my program.

Though i guess if you're just all about quickly producing usable code, stl definitely has its place. And I will agree it's good to know what it has to offer.

Honestly, I'm not so sure how a beginner would respond to looking through stl, though using it may be beneficial to help understand the broad picture of programming logic. Example, using stl's queue classes is very simple, but writing your own would require knowledge over templates, pointers, typecasting, etc. Using stl, one may not be able to write his own queue or understand how it actually works, be he would be able to find practical uses for it and understand when he'd want one.

Not sure if it's a fair analogy...Hopefully you get the point.

I'm a kind of guy: "If somebody already did something, why should I do it again.." And use stl whenever I need to.. And that's pretty much always :P

Making my own low level code takes away from the hi-level dev. The stl code is efficient enough to not make me bother about it.

[quote="cypher1554R"Making my own low level code takes away from the hi-level dev. The stl code is efficient enough to not make me bother about it.[/quote]Start building your own library of code to include in projects and stuff

i agree with keeping your own library of code even if there is a copy of almost the same code out there at least your using your code ontop of that i think if you made the code yourself then it would be easier to just grab at any psuedo random time.

Levio91 wrote:Tell people to familiarize themselves with stl(standard template library) its a great place to start for c++.

I'm not familiar with any standard library things like stacks at all. o_o!
Real men write their own stack classes.