it's not chip. i know where it's happening. in fact, i can always work it out - but i'd work it out faster if i were told. i'm sure it used to be more precise, i thought that i might have pressed something daft.
javac always used to give fantasticly detailed error reports that detailed the whereabouts of the error in every class involved - a great list of errors, but it was always obvious which one was yours (actually, it probably still does. but not for me, i don't really program any java now).