Thread: -,- Deference a scope?

Well, looks like mingw isint as happy about scopes as borland was.

Well, its hard to explain so:

Code:

#include <iostream>
#include <fstream>
#include <string.h>
#include "Definitions.h"
using namespace std;

int LoadScript(string path) {
 ifstream file_in(path.c_str(), ios::nocreate); //Mingw assumes I want std::ios::nocreate.

 if(!file_in) {
  return ERROR_Load_Failed;
 }

 cout << file_in;
}

So, is there some way to termporarialy dereference std so I can use ios?

Do not use a using namespace directive. Still, a solution for your problem without doing that is to specify the global namespace, e.g.,

Code:

#include <iostream>
#include <fstream>
#include <string.h>
#include "Definitions.h"
using namespace std;

int LoadScript(string path) {
 ifstream file_in(path.c_str(), ::ios::nocreate); //Mingw assumes I want std::ios::nocreate.

 if(!file_in) {
  return ERROR_Load_Failed;
 }

 cout << file_in;
}

Hmm, your example didint work. Mingw still assumes I want std::ios instead of just ios::

Code:

 ifstream file_in(path.c_str(), ::ios::nocreate);

When I dont use std, it gets very ugly very quickly. When the file gets bigger it'll be std:: all over. I'd rather not have to do that just over one thing -,-.

Hmm, your example didint work. Mingw still assumes I want std::ios instead of just ios::

That's strange. Could you provide an example that I can test with?

When I dont use std, it gets very ugly very quickly. When the file gets bigger it'll be std:: all over. I'd rather not have to do that just over one thing -,-.

Use specific using directives. If it is a header file, you should fully qualify the names, even if you find it inconvenient.

Code:

#include <iostream>
#include <fstream>
#include <string.h>
#include "Definitions.h"

using std::ifstream;
using std::cout;

int LoadScript(string path) {
 ifstream file_in(path.c_str(), ios::nocreate);

 if(!file_in) {
  return ERROR_Load_Failed;
 }

 cout << file_in;
}

Oh, and your function should return an int. There is a code path where it returns void.

Oh, I didint realize I could specify which headers/functions used a namespace.

That's strange. Could you provide an example that I can test with?

I used basicaly the same code you posted above.

When I specify everything using the proper namespaces, it just says ios is undeclared. I'll just stop being picky and assume the file I'm opening exists >.>.

I used basicaly the same code you posted above.

Unfortunately, only you know what is inside "Definitions.h"

When I specify everything using the proper namespaces, it just says ios is undeclared. I'll just stop being picky and assume the file I'm opening exists

That's because ios is under the std namespace, unless you have your own ios in Definitions.h, which I assumed was the case. Incidentally, std::ios::nocreate does not exist, as far as I know.

Originally Posted by Blackroot

When I dont use std, it gets very ugly very quickly. When the file gets bigger it'll be std:: all over. I'd rather not have to do that just over one thing -,-.

Using std:: all over is the preferred way of doing things anyway.

Personally I think they never should have added "using", it just makes for sloppier code, but that's me.

The other alternative, if possible, is to wrap everything from Definitions.h inside its own namespace, and use fully qualified names for that header file. One of the problems namespaces are supposed to solve is name clashes like the one you're experiencing. This is a good example of why using namespace std; is generally not reccomended outside of toy programs.