Dear Experts, I notice that there are different ways of writing programs. Was wondering if there is anything like a standard which could be used to write good/complete R programs, maintain quality, easy to debug, a standard/practice that can be consistent in an enterprise environment. Also, are there any beacon lights that could help navigate through lines of code, programming styles, understand the scope of a program, identify gaps etc? Thanks, Santosh [[alternative HTML version deleted]]
Check this out: http://www1.maths.lth.se/help/R/RCC/ -- View this message in context: http://r.789695.n4.nabble.com/R-program-writing-standard-practices-tp3588716p3588911.html Sent from the R help mailing list archive at Nabble.com.
On 11/06/11 03:35, Santosh wrote:> Dear Experts, > > I notice that there are different ways of writing programs. Was wondering if > there is anything like a standard which could be used to write good/complete > R programs, maintain quality, easy to debug, a standard/practice that can be > consistent in an enterprise environment. Also, are there any beacon lights > that could help navigate through lines of code, programming styles, > understand the scope of a program, identify gaps etc?This issue was recently discussed on this list. One suggested source of info was http://4dpiecharts.com/r-code-style-guide/ cheers, Rolf Turner