This might sound a bit weird but i really did not get the void concept in book it's given that void is a return type which returns nothing then why to use void?
Campbell Ritchie wrote:The void keyword is not so much a erturn type as an absence of return type.
Exactly what Campbell says. I just want to give you an example that gives the clear understanding of void. In swing/AWT (It could be true for any other Java frameworks. I tested it in Swing/AWT. So, please conside this). For an analogy, We have simple user login page. In this page we are first checking whether user filled username and password or not? If
No then we will simply put a check
else yes then
Create Database Connection
Validate User
And other related user authentication task
So in first check (#1) we say to compiler if something goes wrong then please do not proceed further.
I think that will be sufficient to explain. In case of any doubt please let me know.
God Gave Me Nothing I Wanted, He Gave Me Everything I Needed - Swami Vivekananda
I just had to do a whole project that was filled with entry validation. I didn't throw any exceptions, just returned true or false for good or bad. It seems like Ashish had a similar take on a similar problem. I guess now that you say it exceptions might be good, but I think in a beginner or low level school project, probably not necessary.
When you do things right, people won't be sure you've done anything at all.
John de Michele wrote:I agree with Campbell that exceptions are a much better choice.
John.
I also agree with Campbell's comments but I just want to give a glimpse of void returning situations. It is always as good practice to handle exception rather than simply writing return.
God Gave Me Nothing I Wanted, He Gave Me Everything I Needed - Swami Vivekananda