Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Skyrunner]

Well, sorry for being retarded, I guess. :/

I say use #pragma once if ye compiler supports it, and you don't need to share you project with others. Use #ifndef, #define, #endif if your onpiler doesn't support it, or you need cross-compiler compatiability. Also, you just need to know what it is.

... doesn't your vunderul book have anything about that in it? >.>

[Valid_Dark]

Well I'm not yet at the part in my book about multi sourced projects, and I refuse to skip ahead, but I've just about figured it all out.

Just got my first multi-sourced project to compile with no syntax errors, YAY!
it ended up being a lot easier than I was making it out to be, should have done this sooner.


and Skyrunner, I didn't call YOU retarded,  i didn't mean to call anyone retarded, but I did, and it wasn't directed at you.  I was saying, quoting what someone else said, and telling someone it's an answer to their question, when what was quoted had nothing to do with the problem, is something that a mentally disabled person might do.

Sorry for being mean everyone.  I'll try to be less aggressive in the future.

[Dutchling]

Does anyone have a Python tutorial that they recommend? My newest part-time project uses it

I am using this.

[Sirus]

Does anyone have a Python tutorial that they recommend? My newest part-time project uses it

I am using this.

Thanks, I'll be sure to check it out

[Mini]

Mini, that quote, from Skyrunner, doesn't answer the question I had about global variables,

Whoops.
Original question you asked: Yes, they only have file scope. To access it from other files stick the extern stuff Skyrunner posted about.

[Siquo]

just one thing,  when you declare global variables, they're still only in the scope of that one source file, right?  so instead you should make it a class member variable so you can access it from the other source files, right?   I've been programming with just one source file, my structure is kind of messed up, but I get it now, and just need to restructure a good amount of the code i've already written for this project. (I started it off as a single source project, then realized it was time to get organized)

Yes, they are global only to that file, but using the keyword extern you can "include" them in other files. Static members are the nicer option to globals, but both should be avoided as much as possible. They're too easy to abuse and you'll run into more problems later (Notice how I did not say "never use them").

[kaijyuu]

I WOULD say never use extern, though. Allow access to them through functions, not directly. Will make things far, far easier in the long run.

[Mego]

I WOULD say never use extern, though. Allow access to them through functions, not directly. Will make things far, far easier in the long run.

Never say never. Except when you're talking about goto.

[kaijyuu]

There are seriously a few places I'd use a goto, though really only in switch statements, which are already "almost never" things. (Well actually I *used* to use them there, but some c++11 things alleviated the need for that with some local functions that can inherit local scope. So I guess gotos are back to "never".)

[Mego]

There are seriously a few places I'd use a goto, though really only in switch statements, which are already "almost never" things. (Well actually I *used* to use them there, but some c++11 things alleviated the need for that with some local functions that can inherit local scope. So I guess gotos are back to "never".)

I've never had to resort to goto for anything, even before C++11. Mind giving an example of what you would use it for in C++03?

[kaijyuu]

Occasionally I wanted a few snippits of code to be used for multiple switch cases, and didn't want to use functions for it as it'd lose local scope. Redundant code sucks and I wanted to avoid that, too. So I'd use a goto to jump to a particular case's code whenever I wanted any particular case to use it.

So something like this:

Case 1:
//does blah
goto Case_3;
Case 2:
//do other blah
Case 3:
Case_3:
//do more blah, that's also done by cases 2 and 1
break;

[Mego]

Occasionally I wanted a few snippits of code to be used for multiple switch cases, and didn't want to use functions for it as it'd lose local scope. Redundant code sucks and I wanted to avoid that, too. So I'd use a goto to jump to a particular case's code whenever I wanted any particular case to use it.

So something like this:

Case 1:
//does blah
goto Case_3;
Case 2:
//do other blah
Case 3:
Case_3:
//do more blah, that's also done by cases 2 and 1
break;

I think I get what you're saying, but could you give an example with actual code in it? I'm very curious now, as this might be the first legitimate use I've seen for goto.

[kaijyuu]

That project's long gone, unfortunately :X

The actual use of the switch statement though was enemy behavior in a game. So there were a few different attack states that I wanted to all end in the same way, but had some different starting code. Stuff like that.

[Mego]

That project's long gone, unfortunately :X

The actual use of the switch statement though was enemy behavior in a game. So there were a few different attack states that I wanted to all end in the same way, but had some different starting code. Stuff like that.

Hmm... Why not stick the shared code after the switch statement?

[kaijyuu]

Because not every case would use it. Just some.

(my enemy behavior was all done in the same switch, barring some basic things like movement)