Java tutorial 6 - java input out (io) file reader / writer PART ONE (of 2)

Loading...

Sign in or sign up now!
Alert icon
Upgrade to the latest Flash Player for improved playback performance. Upgrade now or more info.
14,148
Loading...
Alert icon
Sign in or sign up now!
Alert icon

Uploaded by on Jun 28, 2009

Part ONE


In this tutorial I will show you how to read and wrtie data to a file and how to handle the exceptions of our data type value being to large and our file not being found.

Enjoy the video, if you would like to request a tutorial or have any questions please contact me via the youtube messaging services.

DOWNLOAD the files from this tutorial here
http://www.box.net/shared/c1avyc8a5q

Category:

Education

Tags:

License:

Standard YouTube License

Link to this comment:

Share to:
see all

All Comments (21)

Sign In or Sign Up now to post a comment!
  • hi

    

  • how did you do that when you entered the try catch what plugin you useing for notepad++?

  • looking for txt writting information...

  • how the hell did this get 8600 vewis? your video fucking sucked man, not helpfull atall!

  • so the Integer.parseInt(line) ist for Numbers -> what about if I want Strings?

  • this java io not found comes when i try open cmd

  • @pzmtuthcvpvl I find that the BufferedReader/Write are the simplest to use and easiest to remember. Instead of read(), it's readLine() and you store it into a string variable and compare it to null in some sort of while loop.

  • @JFrameMan Honestly, I can't say for certain as I'm only a student and we haven't really gotten into distribution just yet. There are some situations where you wouldn't want to use a wild card though, i.e., two classes with identical names but in different packages. I guess it all depends on the situation.

  • @12eebok ohh i see, thx, i didnt know a lot of that :P lol but when u compile the whole program for distribution as an exe, does it make a difference, since it's not going to be pointing to it, and will running the executable independently?

  • @JFrameMan Nope. Import statements are simply pointers that tell your application where to look. It's actually a better idea to use import java.io.*; because if you import something explicitly you might accidentally define a class with a conflicting name already used in the library, and you wouldn't have to worry about it if you use the wild card.

Loading...

Alert icon
0 / 00Unsaved Playlist Return to active list
    1. Your queue is empty. Add videos to your queue using this button:
      or sign in to load a different list.
    Loading...Loading...Saving...
    • Clear all videos from this list
    • Learn more