On Wed, 28 Jun 2006, Peter Dalgaard wrote:
Paul Gilbert <[EMAIL PROTECTED]> writes:
I've been following this thread hoping for the definitive answer...
Peter Dalgaard wrote:
Well, I do tend to think that we should just use utf, assuming that
people have the relevant glyphs. If they don'
There have been comments from time to time (over many years) on the
inefficiency of the storage of character vectors in R, and R-core has been
looking into the issues. We have some ideas but they would be a
considerable amount of work to implement and it is unclear if they would
actually help
El jue, 22-06-2006 a las 10:37 -0400, Paul Gilbert escribió:
> Iago
>
> I think your R code file needs an .onLoad function. Here is the
> ..onLoad from my dse1 package which is in the dse bundle, as is tframe,
> along with comments which I had forgotten.
>
> ..onLoad <- function(library, se
Iago Mosqueira wrote:
> El jue, 22-06-2006 a las 10:37 -0400, Paul Gilbert escribió:
>
>>Iago
>>
>>I think your R code file needs an .onLoad function. Here is the
>>..onLoad from my dse1 package which is in the dse bundle, as is tframe,
>>along with comments which I had forgotten.
>>
>>..onL
I raised this question quite some time ago but it quitly went down the
river. I'll give it a second try (before keeping my modified version of
matplot for ever...):
matplot supports vectors (and/or character strings) for a number of
arguments namely `type', `lty', `lwd', `pch', `col', `cex'. al
On 28 June 2006 at 16:44, Allen S. Rout wrote:
|
| Greetings. I love R, we run Gentoo. I want to maintain R packages in
| the same methods I use for the rest of them; in Gentoo this is in "the
| portage tree", or in "a portage overlay".
|
| I am working towards something I consider suitable fo
Prof Brian Ripley wrote:
> On Wed, 28 Jun 2006, Peter Dalgaard wrote:
>
>> Paul Gilbert <[EMAIL PROTECTED]> writes:
>>
>>> I've been following this thread hoping for the definitive answer...
>>>
>>> Peter Dalgaard wrote:
>>>
>>>
Well, I do tend to think that we should just use utf, ass
Full_Name: Michael Toews
Version: 2.3.1
OS: Mac OS 10.4.6 and WinXP/SP2
Submission from: (NULL) (24.80.163.133)
This bug also affects related functions (write.csv, etc.), and can be
demonstrated using either a matrix or data frame:
m <- matrix(1:9,nrow=3,
dimnames=list(c("A","B","C"),
I have a general style question about R coding.
Suppose I'm writing a function (foo1) that calls other functions
(foo2, foo3, ...) which have complicated argument
lists (e.g. optim(), plot()), _and_
I may be calling several different functions in the body of
foo1. Since foo2 and foo3 have
On 6/29/2006 12:53 PM, Ben Bolker wrote:
> I have a general style question about R coding.
>
>Suppose I'm writing a function (foo1) that calls other functions
> (foo2, foo3, ...) which have complicated argument
> lists (e.g. optim(), plot()), _and_
> I may be calling several different func
Hi, Paul:
Earlier in this thread, Göran Broström wrote, "I really only need
non-ascii to write the name of the author (me) correctly."
The standard advice I got from a similar thread some time ago is to
use the 'vanilla' Latin alphabet for key words, file and function names,
[Spencer Graves]
> [...] I, too, would like to see all the accents, Arabic script,
> Chinese characters, etc., that other people want to use. However, we
> must work with the world as it is, not as we would like it to be
> (while devoting some time where appropriate to making the world
> bett
Hi Ben,
I have often asked myself such question and often
come back to the following additional options:
(4) Use '...' and ensure encapsulated functions/calls (foo2 and foo3) also
have '...' within their arguments. There is no problem to call 3dspehre with
a list of arguments that include both
13 matches
Mail list logo
