is this bug in windows?

Hi Folks,

one interesting thing, i want you to do/experiment in your windows operating system[I am not sure in linux]

1. create simple a java file [eg: class A{}] say A.java

2. compile it in command prompt so, now A.class

3. rename the A.class file to A.java again

4. and finally try to compile the A.java from command prompt

5. and now

let me know your experience

Not sure what you're getting at. It would result in compilation errors, since it's not a valid source file. What did you think?

Ulf Dittmer wrote:It would result in compilation errors, since it's not a valid source file. What did you think?

please try this yourself.

When I try it, it doesn't compile. Which is what I expected. What do you expect to happen?

Paul Sturrock wrote:When I try it, it doesn't compile. Which is what I expected.

what is the error message ?

I get 87 illegal character compiler errors.

Ah wait, you mean the beeping? That's because some bytes, when printed to the console, cause a system beep. That's not a bug, it's a feature. In fact, there is a character created specifically for this: the BEL character, with integer value 7.

I also get 87 illegal character compiler errors. But I don't understand what is so special in this?

please try this yourself.

I did; what are you getting at? Maybe you meant to post this under Meaningless Drivel :-)

Rob Prime wrote:Ah wait, you mean the beeping? That's because some bytes, when printed to the console, cause a system beep. That's not a bug, it's a feature. In fact, there is a character created specifically for this: the BEL character, with integer value 7.

Ohh. yes I meant this only . but executed in 2 machine.one machine was freezed which has 500MB RAM and another machine it is fine like you guys .

so i thought , it is bug . *sorry for my great misunderstanding* .

anyway thanks for the clarification