Thread: Java error discovered?

Originally Posted by Programming_Hobbyist

Well thanks everyone for the help. Why do you people even post on this forum? Is it the social aspect? It must be the social aspect. Anyway - this is part of my larger project. Now that I can write to file, I can save data to a file, and then retrieve that data. I'm building a project where I can add people, their attributes, and then easily sort them according to attributes, for instance weight, height, eye-color, etc, and then show images of these people according to the sorting criteria.

And that's fine. But this thread is about a specific error, which you continue to insist is a bug "in Java". It's not, and we've demonstrated that several times over now. But instead of saying "okay, my bad, lesson learned", you continue to shift the blame off of yourself as a programmer, which is why people are continuing to try to point out why your conclusion is flawed.

I have tested it for myself. It worked fine. I even posted an example showing you that it worked. All we're asking is that you post the code that you want us to test, and we'll be more than happy to test it. Posting an entire program that contains other logic doesn't really help us, so we've asked several times for an SSCCE. Without that, we have to chalk this up to an error on your part. That's not a personal offense, but hopefully it is a lesson learned: when you see something weird, chances are you're doing something wrong.

Originally Posted by Programming_Hobbyist

I disagree. I think you just have not tested it for yourself. Given that that helloworld already noticed the error with java as well. He didn't call it an error though. I was wrong about try/catch being the source of the error though.

I didn't call it an error in the Java API because that was what was what it was intended to do. I even linked you to the Javadoc for the method which explicitly declares the correct functionality, which we both verified was what happened. Rather the bug was in your code which made assumptions about the Java API which turned out to be incorrect.

You seem obsessed with proving everyone else wrong, when you've clearly provided no counter-arguments to the factual information given to you by everyone else. The API states a behaviour, you experienced that behaviour, it is not an error. Please get more practice in reading the Java API, as you're obviously struggling at the moment.

Originally Posted by Programming_Hobbyist

You people seem to be obsessed with proving me wrong. In fact, you pointed out the error yourself. The write bytes was only writing 1 line of the code - it shouldn't have been. Since I wasn't including the 3rd field, it should've just been creating a new one.

I've heard 20 "you're wrongs" so far - even before people have read my argument. Interesting.

We are trying to help you understand what's going on in your code, since you have a pretty big misunderstanding of how things work. But you keep saying "there's a bug in Java" without actually showing us what you're talking about. Show us what you're talking about, and we'll be more than happy to help you understand what's going on.

It's pretty clear that what happened was you made a programming error or didn't understand the API you were using. That's okay, but it's not a bug in Java. Like I said back in my first reply, resorting to blaming the language or a compiler or a tool instead of yourself is a pretty common novice mistake, and *that* is what we're trying to help you understand.

But if all you want to do is bicker, I can lock this thread. I'd much rather you post the code you're talking about so we can help you understand what's going on, but it's up to you.