1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: EPICS source Documentation - Bloviation inside - don't open unless you want to waste the time |
From: | "Dalesio, Leo `Bob`" <[email protected]> |
To: | "David Dudley" <[email protected]>, <[email protected]> |
Date: | Fri, 8 Sep 2006 09:45:13 -0700 |
As the question must not be serious - I'll state the obvious...... Code always tells the truth. Comments sometimes do not. Documentation says how to use it. Reading the code tells you how to modify it. It is good practice for the comments to at least get you to the modules and subroutine that you are looking for. Once inside - you get what you get. Personally, I write comments for me - I have a short memory. There are very talented programmers that have done a lot of the base code, that do not trust anything but the code. They would read the code regardless of the presence of comments. They obviously don't need comments.