Compilation failures and the exam

[Rajeev Trikha]

I have noticed that I cannot differentiate between {} (curly brackets) and () (parenthesis) because of my eyesight. As many questions have 'compilation failure' as the answer, am I right in saying that the failure is NEVER anything to do with missing matching closures or
deliberate mixing of parenthesis and curly brackets. It is always testing some knowledge point and is to to do with aspects like missing imports, wrong use of generics, using keywords as method names, calling non-static member from static context, not handling a checked exception etc. That is 'compilation error' is checking knowledge of the language and not trying to trick you by eliminating matching brackets. However I do understand that the indentation may be deliberately misleading occasionally.

I hope this advice doesn't breach the non-disclosure agreement.

[Shailesh Phatak]

[Ankit: Please check your private messages for some administrative matter]

[Shailesh Phatak]

i think you should not worry about the parenthesis and curly braces normally but pay little attention for inner class program

[Rajeev Trikha]

Thanks Shailesh. Inner class bracketing is part of language knowledge so I understand the need to work out its scope.

I have never come across the brackets mismatch problem in any simulator but just want to be absolutely sure.