Well that escalated quickly...
Imagine living through it!
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Well that escalated quickly...
CS 271 Computer Organization (4)Can't buy the damn thing until September 8th. Guess I'm getting it from Amazon then.
Logical organization, computer hardware, introduction to assembly and machine language programming.
Prerequisite: CS 162.
Did you consider that the object may be tracking a "current position" in the file? I bet that there is a method to change that position.The innermost stream classes in Java usually don't have seek methods. I'll explain what I think is going on there later.
You are not supposed to randomly hop around in streams. Why? Because seeking back and forth on external memory like HDDs is slow as effing fuck (thousands of times slower than in memory). Hence why streams exist. They work linearily. You start and then work your way through it from start to finish without hopping back all the time. If you need to randomly access the data -> that's why you load the data into a buffer. That one is in memory and you can do what you want with it.Thanks for taking the time to explain that to me. Wish we'd spent time going over that in class instead of trying to figure out just what the fuck the author wanted us to take away in the previous night's reading.
A stream object tracks its position by itself, there is no need to mess with it. If you need to, you are doing it wrong. If you check the documentation on File[Input/Output]Streams linked earlier in the thread you'll also notice that there are overloaded read/write methods that don't need any offsets and indicies, just a buffer and nothing else. Because the library can flush a stream into a buffer or vice versa by itself. It doesn't get any easier.
Some languages excel at one thing over another and it varies a bit depending on what you want to do.
... however I can not ignore the notion of rapid deployment or reliability/heavily bounds checked code (and that does rather exclude C and C++, even with things like Cyclone).
* Implement file I/O for disc image.
* Make a better looking layout for item data editor. If possible fit this layout in a 1024 by 600 pixel frame.
* Incorporate feedback from users at GameFAQs.
* Consider using a JFrame instead of a popup for informational dialogs.
* Implement editors, patching, and file I/O for all known data tables in SaGa Frontier.
* Implement action events to highlight byte/bit GUI components if they deviate from values in base patch.
* Make a changelog generator.
* Make a data table preview generator.
* Make a better readme.
byte buffer = new byte;Maybe I didn't make it clear, but the code above doesn't work. It fails when it attempts tempfos.write(...) while i = 1 (on the second iteration of the for loop, in other words). I stepped through it.
for (int i = 0; i < 256; i++)
int location = i * 28;
zis.read(buffer, location, 28);
tempfos.write(buffer, location, 28);
for (int i = 0; i < 7168; i++)
int writeValue = zis.read();