Just because you have an editor that can let you see the organization within
the file does not mean the code itself is well-structured. If you do put a lot
of code in one file, you will be more likely in your next project that builds
on this one to load code you do not need (bloat), and that is
Hi List,
I'm looking for a rather big, but well structured R file that contains
as much of R language features as possible (i.e. that uses a lot of the
functionality described in the 'R Reference Card' and, if possible, S4
classes too).
I want to check some code I wrote against such a file and
On Tue, Jun 11, 2013 at 11:06 AM, Thorsten Jolitz tjol...@gmail.com wrote:
Hi List,
I'm looking for a rather big, but well structured R file that contains
as much of R language features as possible (i.e. that uses a lot of the
functionality described in the 'R Reference Card' and, if
Sarah Goslee sarah.gos...@gmail.com writes:
On Tue, Jun 11, 2013 at 11:06 AM, Thorsten Jolitz tjol...@gmail.com wrote:
Hi List,
I'm looking for a rather big, but well structured R file that contains
as much of R language features as possible (i.e. that uses a lot of the
functionality
Some would argue that big and well structured are not compatible. Part
of structuring a project well is knowing when and how to break it into
smaller pieces, so those authors who are best at creating well structured R
code will often split it between several small files rather than one big
file.
Greg Snow 538...@gmail.com writes:
Some would argue that big and well structured are not compatible. Part
of structuring a project well is knowing when and how to break it into
smaller pieces, so those authors who are best at creating well structured R
code will often split it between
6 matches
Mail list logo
