I remember similar issue on windows xp with csfml 2.2, but it seems that it was fixed in 2.3
CSFML is not the official SFML library. It is a port/bind which may or may not do things the same way as the official SFML library (Ports/bindings usually introduce their own bugs, quirks and anomalies on top of the official code).Yes, CSFML is one of the official bindings, together with SFML.NET. CSFML is supposed to behave like SFML unless explicitly otherwise noted -- we're glad if bugs or misbehaving features are reported.
There was no such thing, so unless you can start citing all of your insight please stop posting random pieces of 'information'.I totally agree. Please don't spread rumors, it's not helpful in any way.
I'll go further. Don't ever make ANY global object. There is rarely a situation where it's valid.Tell that to the makers of Valve's Source Engine. Tons of globals there, that's kind of where I was getting some inspiration from. I've been programming under the Source Engine for quite a while now. But there's tons of global variables, externs all over the place, and whatnot.
There was no such thing, so unless you can start citing all of your insight please stop posting random pieces of 'information'.I totally agree. Please don't spread rumors, it's not helpful in any way.
This has nothing to do with the topic so please stop posting here.
It was a bug (not only for XP), it was fixed.
Tell that to the makers of Valve's Source Engine. Tons of globals there, that's kind of where I was getting some inspiration from. I've been programming under the Source Engine for quite a while now. But there's tons of global variables, externs all over the place, and whatnot.
The programmers at Valve know what they are doing so I'd say its safe to give them a bit of an exception here :PTypical fallacy: argument from authority (https://en.wikipedia.org/wiki/Argument_from_authority)
It may be related with topic starter issue and may not be related.Because of that it would have been nice to open a different thread and post a link here, so the original discussion can go on uninterrupted. Don't open a thread now -- but thanks for reproducing the issue :)
Tell that to the makers of Valve's Source Engine. Tons of globals there, that's kind of where I was getting some inspiration from. I've been programming under the Source Engine for quite a while now. But there's tons of global variables, externs all over the place, and whatnot.The programmers at Valve know what they are doing so I'd say its safe to give them a bit of an exception here :PTypical fallacy: argument from authority (https://en.wikipedia.org/wiki/Argument_from_authority)
The fact that one big company does something may be the result of various reasons, including historical or political ones -- in short, you don't know the backgrounds. Assuming that it's purely because of better design is risky, and applying the same reasoning to your own code, which has completely different preconditions, is a mistake.
This from a purely logical standpoint. There are objective arguments why global variables are problematic if used too often, see for example here (http://en.sfml-dev.org/forums/index.php?topic=5187.msg34227#msg34227). Please inform yourself carefully and be skeptic what you hear, instead of just thinking "ah, the big guys do it, so it must be right". Most progress in C++ during the decade of C++98 has been made by guys who questioned the common old ways of doing things -- and that was a huge step forward, considering that the language hasn't changed at all until 2011.
Tip: in C++, it's usually better to look at how people don't do things ;)sion can go on uninterrupted. Don't open a thread now -- but thanks for reproducing the issue :)
While I agree with you whole heartedly I'd still like to make the point that global variables are strongly discourages BUT that doesnt mean you cant/shouldnt use them ever, just use them with caution.
Tell that to the makers of Valve's Source Engine. Tons of globals there, that's kind of where I was getting some inspiration from. I've been programming under the Source Engine for quite a while now. But there's tons of global variables, externs all over the place, and whatnot.The programmers at Valve know what they are doing so I'd say its safe to give them a bit of an exception here :PTypical fallacy: argument from authority (https://en.wikipedia.org/wiki/Argument_from_authority)
The fact that one big company does something may be the result of various reasons, including historical or political ones -- in short, you don't know the backgrounds. Assuming that it's purely because of better design is risky, and applying the same reasoning to your own code, which has completely different preconditions, is a mistake.
This from a purely logical standpoint. There are objective arguments why global variables are problematic if used too often, see for example here (http://en.sfml-dev.org/forums/index.php?topic=5187.msg34227#msg34227). Please inform yourself carefully and be skeptic what you hear, instead of just thinking "ah, the big guys do it, so it must be right". Most progress in C++ during the decade of C++98 has been made by guys who questioned the common old ways of doing things -- and that was a huge step forward, considering that the language hasn't changed at all until 2011.
Tip: in C++, it's usually better to look at how people don't do things ;)It may be related with topic starter issue and may not be related.Because of that it would have been nice to open a different thread and post a link here, so the original discussion can go on uninterrupted. Don't open a thread now -- but thanks for reproducing the issue :)