|
So now i come to implement a bit of the File I/O but there's a problem, the program just dies.
Im trying to open a file dflt1, or dflt2, dflt3 dflt4, or maybe tech1, tech2, tech3, tech4... i think you get the idea
Anyways, like i said, it just doesn't work. So i changed the filename to 'reallylongword' and it works fine.
Is there a problem with opening files with short names or something?
|
|
|
|
|
The Undefeated wrote: Is there a problem with opening files with short names...
No.
The Undefeated wrote: ...or something?
Possibly.
Have you considered showing the code snippet that does not work as expected?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
Err, k.
ifstream ReadFile ("M:\\dflt1");<br />
char word[4];<br />
ReadFile.getline(word, 5);<br />
<br />
cout << "Mmm" << word << endl;<br />
ReadFile.close();
That doesn't work
ifstream ReadFile ("M:\\biglongword");<br />
char word[4];<br />
ReadFile.getline(word, 5);<br />
<br />
cout << "Mmm" << word << endl;<br />
ReadFile.close();
That does 
Note that both files have exactly the same content
And you said does not work as expected, it just don't work.
|
|
|
|
|
The Undefeated wrote: char word[4];
ReadFile.getline(word, 5);
Are you expecting this to work (i.e., cramming 5 bytes into a 4-byte spot)?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
WTF? Its an access violation at ReadFile.close()
Am i missing something here? My brain perhaps? Or is this as wierd as i think it is?
Man, i like C# much better - it works
|
|
|
|
|
The Undefeated wrote: Am i missing something here?
I don't know, but I can tell you that it works better to use std::string to read text, rather than a buffer. Asking for more chars than will fit in the buffer is just asking for trouble.
The Undefeated wrote: Man, i like C# much better - it works
Yes, C# is a lot less complex than C++. What C# hides from you cannot be hidden by a language as powerful as C++.
Christian Graus - Microsoft MVP - C++
Metal Musings - Rex and my new metal blog
|
|
|
|
|
The Undefeated wrote: Man, i like C# much better - it works
Yeah, C++ does not work, it is well known in the industry for that. You can find all sorts of articles on the internet about how C++ is broken. None of the software that is written with it actually works either of course. Microsoft just runs all the C++ applications through the C++ to C# converter to get them to run. Sun runs them through the C++ to Java converter and all the Linux stuff is run through the C++ to Linux converter. There is talk of dropping the C++ standard in 2008 for adoption of the "Plain English" compiler. 
led mike
|
|
|
|
|
Uh huh...
Anyways yeah, apart from the slight mistake that i put a 5 instead of a 4, it still doesn't work.
Well, if i try not to close the file it works but, it still doesn't make sense.
And aslo, i have a char array with 9 entire bytes in it, mmm, when i try write it, it so very kindly writes 16 bytes, err... huh?
Im so unhappy 
|
|
|
|
|
How are you writing it ? Is it null terminated ?
Christian Graus - Microsoft MVP - C++
Metal Musings - Rex and my new metal blog
|
|
|
|
|
It is now... but i din't have to do that 4 years ago when a made a lame text-based game with c++
All it was was a load of cin cout, oh yeah.
|
|
|
|
|
You need to study up on how null terminated strings work, it really is that simple... there is no magic. Alternatively you could go back to languages like C# where you don't have to know how null terminated strings work. 
led mike
|
|
|
|
|
I already fixed it, y'know, how i said in the previous post how i've now added a null char to the end.
And we still havn't solved the mistery problem of why readfile.close() crashes the app
|
|
|
|
|
The Undefeated wrote: why readfile.close() crashes the app
Must be more in your app than we know about because this works perfect for me:
ifstream ReadFile("C:\\Research\\HeadersTest.txt");
char line[256];
memset(line, 0, sizeof(char)*256);
ReadFile.getline( line, sizeof(char)*255);
cout << "Line: " << line << endl;
ReadFile.close();
led mike
|
|
|
|
|
Hmmm, no not really, i took out all the other code to test this, must just be one o' thems things, like this one time, i tried to open a file, but the contents was always empty, so i copied the file and opened it, and it worked fine ??? figure that out! (Oh and i tried opening it in various apps, as well as moving the file to a different location, restarting the computer etc.)
|
|
|
|
|
The Undefeated wrote: figure that out!
You were running a "fat" system. I have not seen behavior like that since NT4 workstation and NTFS. I WIN!!
The Undefeated wrote: i took out all the other code to test this
Not what I would do. I would start a "new" project and put "only" that code in it by typing it into the Text Wizard, not by copy-paste.
led mike
|
|
|
|
|
My system aint fat >_< its been on a diet, and it was NTFS
Just so's you know, at the time there wasn't much other code, it would have been exaclty the same.
Anyways, remeber the part where i said it worked when i used long file names? Explain that >_<
Do i win yet?
|
|
|
|
|
The Undefeated wrote: Just so's you know, at the time there wasn't much other code, it would have been exaclty the same.
Ok, so don't take my advice because.... things are going so well when you do it your way.
good luck
led mike
|
|
|
|
|
There's a C++ to Java converter????
|
|
|
|
|
Yes it is in Visual Studio, it's called the "Text Wizard" 
led mike
|
|
|
|
|
Exxxxcellent.
I always knew if I could just convert everything to JAVA all would be well 
|
|
|
|
|
I created a dialog-type MFC app in VS 2005. I created a handler for the OK button so I can cleanup prior to exiting. However, if the user clicks the red X in the upper right of the dialog, my cleanup code is not executed.
How do I create a handler for when the user quits via the X?
Thanks
|
|
|
|
|
Clicking the x acts like the cancel button. You could clean up in a OnCancel() override
as well as OnOk().
Mark
|
|
|
|
|
Mark Salsbery wrote: You could clean up in a OnCancel() override
as well as OnOk().
Which requires "cleanup" code to be in two spots. Why not do it in just one central spot?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
DavidCrow wrote: Why not do it in just one central spot?
I don't know...why not?
That's why I wrote "You could ..." instead of "The only way to do it is ..."
|
|
|
|
|
VFaul wrote: How do I create a handler for when the user quits via the X?
If you want to account for all methods of dismissing the dialog (OK, Cancel, Alt+F4, "X"), handle the WM_DESTROY message.
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
