similar to: R-alpha: generic write()

Hi r-devels, I am a bit puzzled by the behaviour of cat() --- any help is appreciated... At least AFAICS, cat() for vector-valued '...' argument behaves in contradiction to what I understand from the note in the help to cat() which reads " Despite its name and earlier documentation, 'sep' is a vector of terminators rather than separators, being output after every

Kurt writes KH>> * I am also not sure whether one should include the write.table() KH>> function I posted some time ago. It seems to be a bad idea to make a KH>> contrib package out of it (containing only a single function ...). Yes, I think we should have a good "write" function for data.frames. However, I would go even further and 'vote' for a GENERIC

>I have a series of write statements because >i am writing to a file >where the characters strings are the column names of a dataframe >and the numbers are the elements in a particular row. >So, a file might look like > >AAA 2.1 >BB 3.1 >AHLZ 0.2 > >and it would be named "rowname".mls. > >so, each time i get to a new row, i create a new file and

Does anyone know if there is a function available which can format any entered number as words? eg: ''1234'' would be ''One Thousand Two Hundred and Thirty Four'' In the past, I would have said this is a tall order, but from what I''ve seen with playing with rails for a short time, I don''t know what to expect. :) Thanks for any help, Damien

Readers, Scenario: data x consists of one column; 1 2 3 data y; 4 5 6 Is it possible to write to file such that the file is: 1,4 2,5 3,6 using the write.file function? I have tried the command: write(x,file="file.csv",ncolumns=1,append=TRUE,sep=",") write(y,file="file.csv",ncolumns=1,append=TRUE,sep=",") but the result is: 1 2 3 4 5 6 yours,

Looks like I?m bumping a lot into unexpected behaviour lately, but I think I found a bug again, but don?t have access to Bugzilla: Write.table (from core-package utils) doesn?t handle nested data.frames well, the quote arguments only marks top-level character (or-factor columns) for quoting, so this fails: df <- data.frame(a='One;Two;Three',

These days drm core checks function pointers everywhere before calling them. So we can drop a bunch of dummy functions now. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/qxl/qxl_display.c | 50 --------------------------------------- 1 file changed, 50 deletions(-) diff --git a/drivers/gpu/drm/qxl/qxl_display.c b/drivers/gpu/drm/qxl/qxl_display.c index

Call qxl_add_monitors_config_modes() unconditionally. Do all sanity checks in that function. Fix sanity checks. monitors_config is the current monitor configuration, whereas client_monitors_config is the configuration requested by the spice client. So when filling the mode list, based on the spice client request, we need to look at client_monitors_config->count not

Call qxl_add_monitors_config_modes() unconditionally. Do all sanity checks in that function. Fix sanity checks. monitors_config is the current monitor configuration, whereas client_monitors_config is the configuration requested by the spice client. So when filling the mode list, based on the spice client request, we need to look at client_monitors_config->count not

Call qxl_add_monitors_config_modes() unconditionally. Do all sanity checks in that function. Fix sanity checks. monitors_config is the current monitor configuration, whereas client_monitors_config is the configuration requested by the spice client. So when filling the mode list, based on the spice client request, we need to look at client_monitors_config->count not

Call qxl_add_monitors_config_modes() unconditionally. Do all sanity checks in that function. Fix sanity checks. monitors_config is the current monitor configuration, whereas client_monitors_config is the configuration requested by the spice client. So when filling the mode list, based on the spice client request, we need to look at client_monitors_config->count not

Dear R-helpers, I'm trying to develop a function which specifies all possible expressions that can be formed using a certain number of variables. For example, with three variables A, B and C we can have - presence/absence of A; B and C - presence/absence of combinations of two of them - presence/absence of all three A B C 1 0 2 1 3 0 4 1 5 0 6 1

i have a function that returns a list containing a variety of variable types i am trying to run the function multiple times and return the output into a variable with a semi-consistent naming pattern i.e., for ten trials i want to return the list into variables trial1,trial2,...trial10 is there a generic way to get this to happen i have a similar process that does the same thing to an external

Dear all, I have a 10 columns matrix which has 2^10=1024 unique rows, with values 0 and 1. What I would like to do is a little complicated; in a simple statement, for a subset (say 1000 rows) I want to perform pairwise comparisons between all rows, find out which rows differ by only one value, replace that value by "x", get rid of the comparisons that differ by more than one value

Following my posting of a write.table() function, Martin suggested that one could have a generic write() function and special methods for e.g. time series, data frames, etc. Well, a month has passed since ... What does everyone think? Is it a good idea, or would write.table() be enough? If we think that it is not enough, which arguments should the write methods typically allow? What about

Dear Sir or Madam: This is an extension to a earlier post, about looping through several thousand files, and testing student's models against a different data-set, called rclnow, for "recall now". The problem is, that the instructor never specified to the students, what they should name their "lm" object. So what they created was: "arbitrary variable name"

Hi I used write() the other day to save some results. It seems that write() does not record the full precision of the objects being written: > write(pi,file="~/f",ncolumns=1) > pi.saved <- scan("~/f") Read 1 item > dput(pi) 3.14159265358979 > dput(pi.saved) 3.141593 > pi-pi.saved [1] -3.464102e-07 > This difficulty was particularly difficult to

Full_Name: Martin C. Martin Version: 2.7.1 OS: Ubuntu Submission from: (NULL) (75.150.115.86) The function write.arff, in the foreign library: - Can produce relation names with invalid characters - Doesn't use colnames() for attribute names when writing a matrix. Here's a better version: write.arff <- function (x, file, eol = "\n") { if (file == "")

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"), c("I","II","III")))

Hi, I need to resample characters from a dataset that consists of an extremely long string that is written over hundreds of thousands of lines, each of length 50 characters. I am currently doing this by first inserting a space after each character in the dataset and then using the following commands: y <- as.matrix(read.table("data.txt"), stringsAsFactors=FALSE) bstrap <-