2010/8/21 Donald Winston <satchwins...@yahoo.com> > I know how to program in a dozen languages. I have a B.A. in mathematics, > and an M.S. in operations research and statistics.
I just don't care, I would try to answer you even if you had no formation. > I can figure out how to write reports in R. The point is I don't want to. > There should be a function that generates a report just like there is a > function that generates a plot without using loops or if statements. The question is: what do you want? What is the result of this fictive function? I am sure you don't need loop to do that. > I've read "R IN A NUTSHELL" from cover to cover. The word "report" does not > even appear in the index. > Just ask Joseph Adler. > > On Aug 21, 2010, at 11:39 AM, David Hajage wrote: > > > I must repeat: "just show us what is the kind of report you want to > > do, and you will perhaps > > get a solution to reproduce it" > > We still don't know what is the output of your report() function. > > This, is ridiculous. > > > > On Saturday, August 21, 2010, Frank Harrell <f.harr...@vanderbilt.edu> > wrote: > >> > >> > >> On Sat, 21 Aug 2010, Donald Paul Winston wrote: > >> > >> > >> > >> Good grief. Adding a report function is not going to make R less > flexible. Don't > >> you want to use a tool that's relevant to the rest of the world? That > world is > >> much bigger then your world. This is ridiculous. > >> > >> Looks like some people are complaining about me criticizing R and the > people who > >> defend it. Good grief again. > >> > >> > >> I think your philosophy is now more clear Donald. People who don't like > learning new things place themselves at a competitive disadvantage. The R > community, where learning is highly valued, may be fundamentally > incompatible with your philosophy. You may do well to stay with SAS. > >> > >> Frank > >> > >> > >> > >> > >> > >> ________________________________ > >> From: David Hajage-2 [via R] < > ml-node+2333348-1227050197-138...@n4.nabble.com<ml-node%2b2333348-1227050197-138...@n4.nabble.com> > > > >> > >> Sent: Sat, August 21, 2010 4:54:12 AM > >> Subject: Re: R reports > >> > >> Just show us what is the kind of report you want to do, and you will > perhaps > >> get a solution to reproduce it. Then, if you don't like the way to do > that, > >> write your own code or don't use R, noone force you. The majority of R > users > >> are satisfied with the way to generate reports, because it is flexible. > >> There is ABSOLUTELY *NO WARRANTY with R, this means also you have no > >> warranty to find exactly what you want, and what you can find in SAS. > Just > >> deal with it.* > >> > >> 2010/8/21 Donald Paul Winston <[hidden email]> > >> > >> > >> > >> > >> Sweave and LaTex is way to much overhead to deal with. There should be a > >> built in standard report() function analogous to plot(). > >> > >> Something like the following is necessary if you want real people to > take R > >> seriously: > >> > >> report(data=<aDataFrame>, vars=<vectorOfColumnNames>, > >> label=<vectorOfColumnNames>, by=<vectorOfColumnNames>, > >> sum=vectorOfColumnNames>, title=<vectorOfStrings>, > >> footer=<vectorOfStrings>, > >> pageBy=<vectorOfColumnNames>, sumBy=<vectorOfColumnNames>, > >> filename=<string>, fileType=<text|csv|pdf..>...etc) > >> > >> Did I say "real" people? I've been Palinized. > >> -- > >> View this message in context: > >> > http://r.789695.n4.nabble.com/R-reports-tp2330733p2333264.html?by-user=t > >> Sent from the R help mailing list archive at Nabble.com. > >> > >> > >> ______________________________________________ > >> 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. > >> > > [[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.
