Proper library behavior with erroneous user input?

Irrespective of the language used, my general advice is to always fail quickly . This localises errors to the actual source of the problem - i.e. , throw an error or exception and bail out (perhaps permitting the programmer to catch the exception, depending on the language).

Similarly, some languages with checked exceptions might force the programmer to add a check for malformed input.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions