Thread: c++ code errors, need help...

Quote: Originally Posted by ninja9578 I also create libraries in C++ for languages other than C++, so to interface with them, I have to use arrays too. I create DLL's, and within the DLL code itself, you can use anything you want in C++. As Arjay stated, as long as the interface to the function uses arrays, that's all that is needed. Inside the function, you have free reign to do anything you want, use any container you want, etc....

Quote: Originally Posted by ninja9578 Java is ambiguous, maybe not in definition, but when looking at it. Nah, you are just making mistake similiar to what many Java programmers make when they learn C++: you look at the syntax from a C++ point of view, then conclude that it is flawed in Java because you have forgotten what it means in Java. But a Java programmer could take one look at the code and see no ambiguity because the meaning is...

FYI, if you have a vector<int> and an interface like Code: void dosomething(int *array, size_t length); you can always call it like Code: vector<int> myvec(20); dosomething(&myvec[0], myvec.size()); The only special case you need to be aware of is that when the vector is empty, attempting to access myvec[0] may throw an exception under some implementations.

Quote: Originally Posted by icu222much Sorry about that. And thanks for the speedy reply. Why does C++ even have pointers? Why can't it be like Java where you don't have to say if that is a pointer or not? C++ is simply more flexible. In Java you can only create an object with new and will not know when it gets deleted (garbage collection). In C++ you have three choices: You create an object on the stack and it will automatically...

I use stl containers as much as I can , but sometimes I have no choice other than to use an array. I use a lot of old C libraries, which can't accept stl containers as parameters. I also create libraries in C++ for languages other than C++, so to interface with them, I have to use arrays too.

wat

Quote: Originally Posted by Lindley I can't be sure, but I wouldn't expect it to help very much. Why don't you try and find out? I will, since it is in my learning plan, but not just now because I have a feeling that it will involve more reading and time.

I found your problem, and got your program running. The problem is bad design from a stream handling point of view. If I check your program, you tried to open mapIn: - In your constructor - In checkFile - In loadNext Opening your mapIn more than once without closing it will immediately put it into a bad state. (check mapIn.bad(), or just cout << "isBad" << mapIn << endl You have two...

http://www.codeguru.com/forum/showthread.php?t=366302

I've used the first method a fair bit while working with delphi classes as these can't be created on the stack. It never seemd the most elagent solution though. I only mentioned the second method because that was what was shown on cplusplus.com . I've never seen it used in practice. As for the third method. Quote: Originally Posted by D_Drmmr What's undefined about that? It seemed that way because I'm unshore of how...