This resource acts in part as 1.) a declaration of my currently observed coding style convensions, 2.) to serve as a personal and single evolving authority of these convensions and 3.) be a public [for what its worth] undertaking by myself to use these convensions (where mum lets me).
NOTES
This resource tries to follow RFC style and defer to offical IETF resources where possible.
This document occasionally uses terms that appear in capital letters. When the terms "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" appear capitalized, they are being used to indicate particular requirements of this specification. A discussion of the meanings of the terms "MUST", "SHOULD", and "MAY" appears in RFC-1123; the terms "MUST NOT" and "SHOULD NOT" are logical extensions of this usage.
Visit the web-view at Index
Copyright (C) Kyle Younge (2017). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or disclaimers.
This document and the information contained herein is provided on an "AS IS" basis and the authors, ie. Kyle Younge or contributors, ie others DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
These guidelines are in part are an aggregation of every sensible developer and engineer I have worked with.
THANK YOU!