And at the mention of the keyword "Java", I'll jump in and say "It's great!!!" - even if slightly off topic...
It really does just take time and a bit of practice to realise what the Java compiler is telling you, once you know what you're looking for (and heaven's sake - it even
tells you what
line the error's on
; alternatively, if it's a runtime error, you can easily use "printStackTrace()" to track the error back to the rogue line and deal with it that way
). Don't get me wrong though -
all compiler messages are cryptic, if you aren't fully au-fait with the language you're using
. However I do admit, that "Cannot resolve symbol" is
just a touch on the "ambiguous" side for most people
Just my two pennies worth...
-Jackpot
PS: Flirbnic's comment made me smile
and grimace about the one time that happened to me...
------------------
"lucky_jackpot is the smily god..." - gothicX
"Life is mostly froth and bubble,
But two things stand in stone,
Kindness in another's trouble,
Courage in your own"
("Ye Wearie Wayfarer" - by Adam Lindsay Gordon)