this compiles but crashes! i cant find my mistake (this is the entire code so far)
ps: it gives no error code, just opens and close instantlyCode:#include <iostream> #include <vector> using namespace std; int main(){ vector<int> list; int counter,temp; do{ cout<<"Please enter a list of number, -1 to quit"<<endl; cin>>temp; list.push_back(temp); }while(temp!=-1); return 0; }
Last edited by MarlonDean; 05-19-2008 at 03:48 AM.
Probably because you're not entering -1, so the loop quits. Once the loop quits, the program then quits since there is nothing left to do but return 0. There is no crashing. It's just ending because you didn't write your loop condition proplery.
but isnt it suppose do to the cout statements at least once? Is that the point of using a do... while?
Actually, I misread that. I must be a little blind tonight. The code looks relatively fine, outside of poor indention.
I even ran it myself, and it appears to work.... I don't know what your problem is. Sorry.
Aside from going into an infinite loop on entering a non-number, the code is fine. Are you sure that's exactly what you're compiling?
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
This isn't your problem here, but avoid "using namespace std", especially when declaring variable names that are type names in the standard namespace (e.g. list). It's a bad habit to get into.
I dont know works perfect to me try using a different compiler
Yes, the problem is my compiler, if i save a file, i must not have a space in the filename eg. project 1.cpp will cause my program to flash
I'm sure the compiler will cope with spaces in the filename, but you may need to quote the filename, e.g.Originally Posted by MarlonDean
If you use:Code:gcc "my file.c"
the compiler will try to compile "my" and "file.c" which will not do the right thing for you if you have a file called "my file.c".Code:gcc my file.c
If you use an IDE that doesn't cope with spaces in filenames, that's a bug in the IDE.
Finally, I would say it's a BAD idea to use filenames (or directories) with spaces for programming projects. It tends to lead to all sorts of interesting effects.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
On a side note, Visual Studio seems to handle spaces in files fine. MFC sometimes tends to generate files with spaces inside. I can't vouch for other IDEs/compilers.
Welcome to the future, manav. The future where IDEs compile our files for us so we don't need to use scripts or command line.
Both have their benefits. There are some really powerful solutions using command-line tools. Other things are much easier and better done in the IDE. It's not an "all or nothing" situation, there is a choice, and it's not that you can't choose for each individual task which one would work best.
A lot of people who don't use command line do so because they simply have never learned how to use the tools that are available there. There's also the problem that many of the OLD DOS and Windows equivalents of the Unix tools where not quite as good as the Unix equivalents.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
Command lines are definitely outdated now, especially for Windows (maybe not for Linux).
There are tools that can generate scripts and the like, so you won't have to do it by hand. A good GUI will not care if the filenames contain spaces or not.
A library that requires you to compile your project via a makefile is a bad library. A good library can optionally support both.
Command lines are tricky and error prone (remember screwing up C++ exception handling due to compiling via the command line?).
That is your personal opinion, and you are entitled to it. I use command line a lot in Windows, it works just fine and does what you want, and building Windows drivers is completely done with command-line tools provided by the Windows DDK. Yes, you can make the Visual Studio IDE run the command line tools for you, but it's not running the standard IDE build tools.
As to getting options correct, you can get that right and wrong in both command line and IDE - if you don't set the right options [and figuring out WHAT IS RIGHT is a bit part of that puzzle] in either of them, you don't get what you wanted. It makes absolutely no difference if you have to select a box in an IDE or type in /EHsc [or whatever option you happen to want to use] on the command line - whichever way you do it, you still need to get it right.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
While the original thing I was aiming for was that the IDE will set the default options for you and pass them to the compiler wheras with the command-line compiler, you have to set those manually because those options will default to OFF or whatever if you don't specify them.
So it's less error prone to use visual studio to compile instead of the compiler. This fact was eventualized by the fact that manav compiled wrong because he was given the incorrect information (or as some say, failed to read the manual) about which command lines should be used. Had he compiled using the IDE instead, he would have received no such thing.
(Further to note that he did ignore the warning generated by the compiler also suggests that he failed to read the manual properly.)
