Yes! Do it, I'm a newbie!
Yes. Stop the cluttering of the boards.
Yes. (other reason).
No! Don't waste the server space!
No. Let the newbies fend for themselves.
No. (other reason).
Who here thinks that......
Lately, I've been seeing "I/O" this and "I/O" that in the windows programming section. These are obviously newbies posting such messages. Alas, I too once was a newbie, and was surprised at what effort it took to learn to successfully compile one line of code. Shouldn't someone start a tutorial on file i/o for those poor newbies? What about posting it on cprgramming.com for them? Should some on do this?
Weeel, itss aboot tieme wee goo back too Canada, eeehy boyss.
I might be wrong...but isn't there one already in the FAQ? If there isn't, then by all means, yes there should be a file I/O tutorial on the page...but I said no because I think there might be one in the FAQ...
i'm all for the I/O tute... it'll be great to not have to read throughall those crap cluttering posts...
From time to time it might be a good idea to check out the Tutorials made by the Webmaster before posting...There is a File I/O tutorial by the webmaster in the Tutorials Section:
http://www.cprogramming.com/tutorial.html
Number 10.
the problem is, how many n00bs actually read that?
i bet it's less that 1 in 10
Why don't you just redirect messages with the I/O string to
the tutorial first?
rick barclay
No. Wait. Don't hang up!
This is America calling!
Even if there wasn't a tutorial in file I/O there shouldn't be, it's way too easy to find that out for yourself (I did)
You should use that space on more advanced tutorials, such as video, audio, modem, Internet, networking or something like that...
Oskilian
Last edited by oskilian; 10-23-2001 at 07:18 PM.
I see that there iss already an i/o tutorial on the FAQ, but... It doesn't really lead up to newbies who are wanting to design a win32 gui. A newbie would read this, compile it, and say, "Thats a DOS program (gasp!!!), I must be a super programmer overnight, by golly!!!!! Besides, what n00b knows to include the correct header file? Well, i guess that i might be under estimating the n00bs, but oh well. I along with numerous others are tired of seeing the crap every two posts about i/o'ing with dialog's & edit box's. I know that i too once posted an i/o question, but again, oh well.
Weeel, itss aboot tieme wee goo back too Canada, eeehy boyss.
We need to FAQ it because it is a FAQ. I stated this a year and a half ago.
Blue
that is so true.
FAQ is the newest verb in the english language.
a definition will come in following posts when i'm board enough to actually make one up...
Hmm..
cout = screen output
cin = keyboard input
Think out of the box! Open Source rules!
-Breach23
ohhh, but it goes so much deeper than that...
operator overloading with the insertion and extraction operators, FILE i/o, and oh so much more.
oh so many things that n00bs will post a lot of inane rubbish about because they down't understand the current faq.
>>Hmm..
cout = screen output
cin = keyboard input<<
No... what I am talking about here is fstream components. Many many newbies ask how to output text to a file, read text from a file, write text from one file to another, etc etc etc.
It is a frequently asked question. We have a frequently asked question section. Therefore it is more than a tutorial.... it is a FAQ. Does this make sense to anyone else?
The FAQ should go over opening both an ifstream and ofstream object and perhaps cover .get() and .put() since those are easy fstream components to comprehend.
You get one character from a file and put it in the other file. This type of explanation covers multiple concepts about C++ standard file streams.
Do you all agree?
Blue
o...either read the fact, or read the MSDN library...pretty useless here...
Think out of the box! Open Source rules!
-Breach23
