Thread: Ask/Tell about --- Coding. Programming. General script writing.

Blue hey, do you think I'll lose anything if I start out with microsoft visual basic?

I decided it would be easier since it gives you free tutorials with download.

Originally Posted by Sandform

do you think I'll lose anything if I start out with microsoft visual basic?

respect

I kid, I kid....

Originally Posted by Ynot

respect

I kid, I kid....

Is it that bad? lol.

Pyrofan1: Thanks! That's exactly the kind of thing I was looking for, and it looks like it's easy to understand.

ninja 9578: Yeah, I've noticed C++ is tough to learn. I've considered learning Python instead, but I've already finished a class at my high school teaching C++, as well as spending hours learning more on my own, so at this point it's probably more convenient for me to just continue with C++ rather than switch to another language, even one as similar to C++ as C.

You have those at your school? Lucky!

Yeah, seriously. Most school start off with Java.

I don't think anyone really uses Python other than Linux developers I might be wrong, but I don't think it's very useful to know.

Originally Posted by ninja9578

I don't think anyone really uses Python other than Linux developers I might be wrong, but I don't think it's very useful to know.

oh gawd,
now you've done it.....

Originally Posted by Ynot

just a few things,
avoid using "using"
I know all the tutorials use it, but it can bite you in the arse
(it pulls all the functions and objects into the current namespace, and can lead to naming conflicts)
personally, I think it's really bad practise
but others may say different

You are correct.

Originally Posted by Seismosaur

'Using namespace std/ w/e' saves time writing out std:: and minimizes the chance you'll mistype std::cout or cin or whatever you are using.

You are also correct.

Go the middle road: instead of bringing the whole namespace into scope, bring individual directives.

So instead of typing using namespace std;, you type using std::cout;, etc. Then when you want to use a specific but not-so-oftenly-used item within a namespace other than the one that's been brought into scope, you clarify it in full.

That way you keep the scope resolution clean of unneccessary clutter and you save time by keeping frequently-used constructs in scope while fully qualifying the rare ones.