It looks like I can store each function in a different file and have "main 
file" containing the "include-like" directiives and the 
main instructions. Something like:

source("Program_Global_Constants.R")
source("Program_Global_Variables.R")
source("Program_Fun1.R")
source("Program_Fun2.R")
source("Program_Fun3.R")
source("Program_Fun4.R")

#.............................................................................................
#........................................ Main 
..............................................
#
  Fun1()
  Fun2() 
  ...........
  Fun4()




-----Messaggio originale-----
Da: jgar...@ija.csic.es [mailto:jgar...@ija.csic.es]
Inviato: gio 23/04/2009 11.39
A: mau...@alice.it
Cc: r-help@r-project.org
Oggetto: Re: [R] how to split and handle a big R program into multiple files
 
source() and the use of functions
...
Javier
---

> I am working on a program totally written in R which is now getting bigger
> and bigger so that editling the only file that contains all the functions
> is becoming more and more unmanageable.
> I wonder whether it is possible to spread the R code, making up the same
> program, in a number of smaller files and then call them all, in the right
> order, through a list of something like the C language <include>
> directive.
>
> Any other suggestion how to organize, handle, and maintain a big R program
> is welcome.
>
> Thank you in advance,
> Maura
>
>
> tutti i telefonini TIM!
>
>
>       [[alternative HTML version deleted]]
>
> ______________________________________________
> R-help@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide
> http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
>





tutti i telefonini TIM!


        [[alternative HTML version deleted]]

______________________________________________
R-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.

Reply via email to