similar to: bug: write.dcf converts hyphen in field name to period

Full_Name: charles blundell Version: 2.7.0 OS: Debian GNU/Linux Submission from: (NULL) (217.37.73.202) The Debian Policy Manual says concerning lines in a Description field: * Those containing a space, a full stop and some more characters. These are for future expansion. Do not use them. (section 5.6.13, http://www.debian.org/doc/debian-policy/ch-controlfields.html) But for example: >

Full_Name: Bill Dunlap Version: 2.5.0 OS: Red Hat Enterprise Linux WS release 3 (Taroon Update 6) Submission from: (NULL) (24.17.60.30) If you read a dcf file with read.dcf(file,fields=c("Field",...)) and the file does not contain the desired field "Field", read.dcf puts a character NA for that entry in its output matrix. If you then call write.dcf, passing it the output of

BIll, Thanks. I am seeing some problems here, for example when all the fields are missing, or all the fields in a row are missing. I've fixes for those, and will commit to R-devel shortly. On Tue, 17 Jul 2007, bill at insightful.com wrote: > Full_Name: Bill Dunlap > Version: 2.5.0 > OS: Red Hat Enterprise Linux WS release 3 (Taroon Update 6) > Submission from: (NULL)

The change in r42731 eliminating the final blank line when writing DCF files changes the way 'append' can be used in 'write.dcf' and I was wondering if this is intentional. Basically, I want to write a data frame to DCF format one row at a time, so I make use of repeated calls to 'write.dcf(append = TRUE)'. However, in R 2.6.0RC the resulting DCF file is not formatted

I don't know if this is a bug per se, but an undesired behavior in read.dcf. read.dcf takes a file argument and passes it to gzfile if it's a character: if (is.character(file)) { file <- gzfile(file) on.exit(close(file)) } This gzfile connection is passed to readLines (line #39): lines <- readLines(file) If no newline is at the end of the file, readLines

Hi, read.dcf() can modify the locale variable LC_CTYPE, and here is a minimal example: > Sys.getlocale('LC_CTYPE') [1] "en_US.UTF-8" > read.dcf(textConnection('a: b'), all = TRUE) a 1 b > Sys.getlocale('LC_CTYPE') [1] "C" After diagnosing the problem, it seems the on.exit() call in read.dcf() is the culprit:

To Whom It May Concern: I have noticed that all of the hyphens ("-") are changed to periods (".") when I try to read.table() and the headers contain "-" I am using R 2.13 on a RedHat system. Here is the situation: I have the following a tab-delimited text file saved as test.txt File1-a.txt File1-b.txt File2-a.txt File2-b.txt 1 1 2 1 1 2 3 2 1 1 2 3

Hi, on all my systems update.packages() and install.packages() fails now. I get the following message: root at orca:/root(28)# R R version 2.10.1 (2009-12-14) Copyright (C) 2009 The R Foundation for Statistical Computing ISBN 3-900051-07-0 R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type 'license()' or

Dear R devs, I would like to raise a request for a simple helper function. Utility function to extract package dependencies from DESCRIPTION file. I do think that tools package is better place, for such a fundamental functionality, than community packages. tools pkg seems perfect fit (having already great function write_PACKAGES). Functionality I am asking for is already in R svn repository

I'm seeing a segfault on x86_64 Linux with the following code: desc = read.dcf("BAD") con = gzfile("test.gz", "wt") write.dcf(desc, file=con) close(con) where BAD has a long field (see below for example). The crash happens inside dummy_vfprintf. I think the issue is that the va_list ap is modified by the first vsnprintf call

Dear R-Users, I'm trying to setup a personal repository for a few packages I'm working on. I am on R-Forge but I still need to have various versions of my package that R-Forge does not build (for R 2.8.1 for example). So I followed the instructions in this document: Hhttp:// cran.r-project.org/doc/manuals/R-admin.html#Setting-up-a-package-repository and used this function as

Was looking at what was output for <pkgname>-package.Rd and wondered if any there was any means (via macro, etc) to merge some of the same information with a template for my package manpage? As much (all?) of the generated information was already provided in the DESCRIPTION, I'd prefer not to have to update the information in multiple places. I'm thinking here that I could provide a

Thank you Gabriel, Just for future readers. Below is a base R way to address this common problem, as instructed by you (+stopifnot to suppress print). Rscript -e 'stopifnot(file.copy("DESCRIPTION", file.path(tdir<-tempdir(), "PACKAGES"))); db<-available.packages(paste0("file://", tdir));

Hi all, I have a data.frame with the following colnames pattern: x1 y11 x2 y21 y22 y23 x3 y31 y32 ... I.e. I have an x followed by a few y's. What I would like to do is turn this wide format into a tall format with two columns: "x", "y". The structure is that xi needs to be associated with yij (e.g. x1 should next to y11 and y12, x2 should be next to y21, y22, and

Hi all, I've come across an issue caused when I try to set the query parser's default op to OP_PHRASE: Xapian raises an Unimplemented Error if the query contains hyphenated words or other terms that implicitly generate a phrase. This can be shown with the following Python extract: >>> from xapian import * >>> qp = QueryParser() >>>

imagen1 MEDICI?N POR TELEMETR?A DE VOL?MENES DE AGUAS NACIONALES Aplicaci?n de la NMX-AA-179-SCFI-2018 ??nete a nuestro curso online de capacitaci?n sobre la medici?n por telemetr?a de vol?menes de aguas nacionales y aplicaci?n de la norma NMX-AA-179-SCFI-2018! Fecha: 23 de Julio Duraci?n: 6 horas Modalidad: Online En este curso, aprender?s las t?cnicas m?s avanzadas para medir vol?menes de

On Wed, Jan 16, 2013 at 12:04:52PM -0500, Stephen Checkoway wrote: > > On Jan 16, 2013, at 10:07 AM, Brad Smith <brad at comstyle.com> wrote: > > > I was wondering if someone with more familiarity with MC > > on X86 could consider looking into adding support for > > the hyphenated versions of the VIA Padlock instructions? > > > Take a look at

I was wondering if someone with more familiarity with MC on X86 could consider looking into adding support for the hyphenated versions of the VIA Padlock instructions? If anyone is up for it there are details within these two bug reports.. http://www.llvm.org/bugs/show_bug.cgi?id=8556 http://www.llvm.org/bugs/show_bug.cgi?id=10266 -- This message has been scanned for viruses and dangerous

On Jan 16, 2013, at 10:07 AM, Brad Smith <brad at comstyle.com> wrote: > I was wondering if someone with more familiarity with MC > on X86 could consider looking into adding support for > the hyphenated versions of the VIA Padlock instructions? Take a look at llvm/lib/Target/X86InstrSystem.td perhaps. -- Stephen Checkoway

Dear R-developers, I would like to suggest a 'method' slot for format.ftable() (see an adjusted 'format.ftable()' below, taken from the source of R-2.15.2). At the moment, format.ftable() contains several empty cells due to the way the row and column labels are printed. This creates problems (= unwanted empty columns/rows) when converting an ftable to a LaTeX table; see an