C++ Tutorials - Absolute n00b spoonfeed

and point to them? which is better. interms of the machine or w/e

You should never declare them globally, it's awful programming practice (same with using "goto"s)

Always declare them locally; preferably you'll have classes and such to encapsulate your variables a little more.

Yea but do you know why???
Ignoring security...

Its all part of the new generation of organizing your data & routines (variables & functions) amongst other such programming solutions like OOP. Objects should remain belonging/existing only where they are needed and used, not exposing everything to anyone/anywhere/anytime.

HOLY SMOKES! no GOTO's ????????

now what?

Zorro, thats true.

Antirtfm I see.

so It seems like its only a program structure and arrangement thing and not a machine thing.
I'll take it that the machine doesnt care if they are global or not, and wont make much difference even on a large scale. am I wrong.

mooseader whats the argument about goto's??

They shouldn't just be declared locally, they should be declared near first use - even if near the end of a function.

There is a performance loss to declare them globally, not to mention bad coding practice as Moosader said but also on more of a technical side (Globally declared variables being in the .data segment of a file, for example)

-----

As far as I know there really isn't any technical disadvantage to GOTO.

If you're at the point in a function where you need to use GOTO, There is probably a much better way you can write it.

But as Moosader said again, It's bad coding practice.

To quote the C++ FAQ: "Code must be written to be read, not by the compiler, but by another human being. "

Like Vevix said write better for you to read, If you have a big program going and you start tossing in goto's you can very easily get stuck in a infinite loop. gotos are a old program deal and using them now will make you look like a poor programmer with poor design.

basically, when people use gotos, it makes their code a tangled, ugly, hard-to-follow mess. Therefore, it's bad programming practice.

Unless you're writing in Assembly, anyway. Then it can't be helped.