[DPP-Devel] Is defensive programming an unspoken guideline in Saros?

[Arsenij E Solovjev]

Hello dear devs,

Whenever I look at Stefan's comments on reviews, half of them refer to 
either:
a) null-checks
b) thread safety
AFAIK, that's just defensive programming. Defensive programming (again 
afaik), that
as you code you are paranoid that every line of code that you write 
might lead to a
disaster of unspeakable proportions. And rigorously reinspect what 
you've written,
adding handling for possible errors as you go.

Would it help to *explicitly* address defensive programming as a 
desirable style in our
coding conventions [link <http://www.saros-project.org/coderules>]?
Could Stefan perhaps write how he see this and perhaps a summary of the 
most
common pitfalls that we do?

Cheers,
Arsenij
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel