similar to: foreign:::writeForeignSAS patch not released?

Attached is a patch to fix https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17256 'possible bug in writeForeignSAS in the foreign library when string is NA' The patch 1. fixing the case where there were NA within a character column, and the case where all values are strings of length 0 2. general replacement of calls to `sapply` with `vapply` (and replacing any(is.na()) with

>>>>> NELSON, Michael <mnels at doh.health.nsw.gov.au> >>>>> on Thu, 17 May 2018 11:53:27 +0000 writes: > Attached is a patch to fix > https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17256 > 'possible bug in writeForeignSAS in the foreign library > when string is NA' > The patch 1. fixing the case where

Dear R-devel, I've made some potential extensions to writeForeignSAS in 'foreign' that I wanted to pass along if anyone is interested. I've attached the diff -u output against the version found in foreign_0.8-15 and an .R file with my changes. (In this .R file, the function is named writeForeignSAS7 to simplify testing/comparisons.) I've tried to alter the current

here appears to be a bug in the foreign library. The following code used to work, but now generates an error when 'package="SAS"' is specified: ds <- read.csv("http://www.math.smith.edu/sasr/datasets/help.csv") # running foreign package version 0.8-30 library(foreign) # this works fine write.foreign(ds, "foo", "bar", package="Stata") #

I tried to use write.foreign() to export to SAS this morning and got an error. When I looked at the code for writeForeignSAS() I saw this line: dfn < -df which I think should be dfn <- df So, I tried to run update.packages() to see if there was an updated version and got the following result. > update.packages(c("foreign")) Warning message: In list.files(lib) :

Dear all, First of all, I thank you for the creation of the package. I write this message concerning the write.foreign() function from the foreign package and a bug that I discovered. When we want to save our dataset as a .sas file, the limit of variable names character is 8 by default. In SAS this limit is 32 character and an argument in the function, validvarname, can theorically switch the

Hi R experts, I have a problem in Write.foreign command (SAS). I have a data frame called d. >d Datetime 2006-12-01 00:00:00 2006-12-01 00:10:00 2006-12-01 00:20:00 2006-12-01 00:30:00 2006-12-01 00:40:00 >class(d$Datetime) [1] "POSIXt" "POSIXct" Then I tried with, write.foreign(d,"Z:\\try_i.sas7bdat"," Z:\\try_i.sas

Hello, Most likely I'm doing something wrong, but am at a loss as to what the issue is. I have a clean checkout of trunk here: ?? ~/svn/r-devel/R$ svn info ?? Path: . ?? Working Copy Root Path: /home/btyner/svn/r-devel/R ?? URL: https://svn.r-project.org/R/trunk ?? Relative URL: ^/trunk ?? Repository Root: https://svn.r-project.org/R ?? Repository UUID:

Hi experts, I have a problem in Write.foreign command (SAS). I have a data frame called d. >d Datetime 2006-12-01 00:00:00 2006-12-01 00:10:00 2006-12-01 00:20:00 2006-12-01 00:30:00 2006-12-01 00:40:00 >class(d$Datetime) [1] "POSIXt" "POSIXct" Then I tried with, write.foreign(d,"Z:\\try_i.sas7bdat"," Z:\\try_i.sas

Hi, after updating to foreign version 0.8-32, I experienced the following error when I tried to load a SPSS file: Fehler in inherits(x, "factor") : objekt "cp" nicht gefunden Zus?tzlich: Warning message: In read.spss("***l.sav", use.value.labels = TRUE, to.data.frame = TRUE) : ***.sav: File-indicated character representation code (1252) looks like a Windows

Hans, I'd like to make sure that I'm using the right LLVM version. I tried to download LLVM 8 from the link in your email by cloning this repository: git clone https://github.com/llvm/llvm-project.git When I do llc --version, it says LLVM 9.0.0 instead of 8.0.0 LLVM (http://llvm.org/): LLVM version 9.0.0svn DEBUG build with assertions. Default target: x86_64-unknown-linux-gnu

Hi all, I have jut installed the foreign package (v 0.8-8) on my OS X machine, and have a bit of a problem writing out a data frame in SPSS format. Specifically, the code file (the .sps format file) seems to write 3 unprintable hex values instead of double quotes. For example, in the following output ... VALUE LABELS / immDel 1 ###1### 2 ###2### 3 ###3### ... emacs tells me that

Hello, does anyone have experience with reading SPSS Version 15.0 files into R (version 2.4.1, WinXP)? I have long been sucessfully reading SPSS files with read.spss from the wonderful foreign package, but somehow after upgrading from SPSS14 to SPSS15 I seem to have problems. Trying a simple example, where test.sav is a SPSS 15.0 data file consisting of x1=c(1,2,3) and

I encountered something strange with read.spss (package foreign, version 0.7 with R2.0.0 and version 0.8 with R2.0.1 beta, windows XP) I made a test file test.sav with SPSS version 11.5.1 containing only one numeric variable, with a value label for one value not occuring in the file. According to ?read.spss this should result in a factor, but it results in all NA. Using the argument

Hi, I follow different setup instructions and I can't make imap-hibernate work. I've tried vmail and dovecot as users, tried to set mode to 0666, without success. I'm using FreeBSD 11.2. Is imap-hibernate compatible with FreeBSD 11.2? My operational system: # uname -v FreeBSD 11.2-RELEASE-p9 #0: Tue Feb 5 15:30:36 UTC 2019 root at

Hi All, Sorry that I didn't provide enough information. I've been trying to import SAS xport files that contain multiple files using package foreign's read.xport. I first attempted this back in 2005 and had problems. Some of files that were present in the SAS xport file weren't being created in R. I submitted my problem to the community:

I'm pleased to announce that LLVM 8 is now available. Get it here: https://llvm.org/releases/download.html#8.0.0 This release contains the work on trunk up to Subversion revision r351319, plus work on the release branch. It's the result of the LLVM community's work over the past six months, including: speculative load hardening, concurrent compilation in the ORC JIT API, no longer

I'm pleased to announce that LLVM 8 is now available. Get it here: https://llvm.org/releases/download.html#8.0.0 This release contains the work on trunk up to Subversion revision r351319, plus work on the release branch. It's the result of the LLVM community's work over the past six months, including: speculative load hardening, concurrent compilation in the ORC JIT API, no longer

Thanks, Brian I tried enabling both the lld and the clang projects by adding -DLLVM_ENABLE_PROJECTS='lld;clang' into the cmake command. After the build completed successfully, I can see ld.lld in my bin folder but not clang. Is it supposed to be in another folder? Thanks. ________________________________ From: Brian Cain <brian.cain at gmail.com> Sent: Wednesday, March 20, 2019

On 21/04/2019 4:56 p.m., Benjamin Tyner wrote: > Hello, > > Most likely I'm doing something wrong, but am at a loss as to what the > issue is. I have a clean checkout of trunk here: > > ?? ~/svn/r-devel/R$ svn info > ?? Path: . > ?? Working Copy Root Path: /home/btyner/svn/r-devel/R > ?? URL: https://svn.r-project.org/R/trunk > ?? Relative URL: ^/trunk