similar to: Correction to PR #9631 (PR#9632)

Hi! I need to import in R some SAS dataset (sas7bdat). I found two functions to do it: "read.ssd" from the package "foreign" and "sas.get" from "Hmisc". df = read.ssd(libname = path2data, sectionnames = "sasSmallDataset", tmpXport = path2data, tmpProgLoc = path2data, sascmd = path2sas) sas.get(libraryName = path2data, member =

Full_Name: Jeff Hallman Version: 2.4.1 OS: Linux Submission from: (NULL) (132.200.32.34) read.ssd() invokes PROC COPY to create an xport file, but PROC COPY has some annoying limitations that read.ssd() should deal with. The first is that PROC COPY doesn't work with member names (the sectionnames argument to read.ssd) longer than 8 characters. The second is that PROC COPY also fails if any

I am attempting to read in a SAS 9.1 data file. After starting R I change to the directory containing the sas data file and use the "dir" command to confirm that it is there. Then I run the following R-code: library(foreign) sashome <- "/Program Files/SAS/SAS 9.1" test<-read.ssd(file.path(sashome), "pcb", sascmd = file.path(sashome,

Hello, I have a beginner's Q: if i want to know all the functions provided by a package, what is command for that? in another word, Is there a command to list all the commands available in a packege? thanks a lot, yan

Hi I am having trouble using read.ssd. Can someone help? The code that I have written is *sashome<-"C:/Mary/Datasets"* *read.ssd(read.ssd(file.path(sashome, "core", "sashelp"), "surv_1v",* *sascmd = file.path(sashome, "sas.exe"))* Here the path that I have given is correct, where the dataset surv_1v.sas7bdat is kept. The message that R gives

Hi, I was reading e-mail about one doubt that you were when you read files .sas7bdat in R. Now, I am with the same problem. But I don?t know how can i do that. I have download de Sas Viewer and i am using this sintax in r: > read.ssd("X:\\users\\Anresc07","que0411.sas7bdat") SAS failed. SAS program at C:\DOCUME~1\leandro\CONFIG~1\Temp\RtmpXR1Tid\file3d6c4ae1.sas The log

Hi all, I have a large (approx. 1 GB) SAS dataset (test.sas7bdat) located in the server (“R:/” directory). I have SAS 9.1 installed in my PC and I can read the SAS dataset in SAS, under a windows environment, after assigning libname in "R:\" directory. Now I am trying to read the SAS dataset in R (R 2.12.0) using the read.ssd function of the “foreign” package, but I get an error

Hi, I am trying to read a SAS version 9.1.3 SAS dataset into R (to preserve the SAS labels), but am unable to do so (I have read in a CSV version). I first created a transport file using the SAS code: libname ces2 'D:\CES Analysis\Data'; filename transp 'D:\CES Analysis\Data\fadata.xpt'; /* create a transport file - R cannot read file created by proc cport */ proc

I am very new to Rails. After skimming through the documentation over the last several days, I''m struggling with the appropriate use of belongs_to. My main question is whether a model can have several belongs_to declarations. I have not seen any examples online show that usage. If it can, then I would like to know if it''s poor form or what the best practices are around

Dear all, I want to start my post by expressing my sincere gratitude for all the help this group has given me in Sweave/Latex/R. The tools are excellent and so is the community! On to the question. My Sweave code is intended to make lots of plots and create a *.pdf document. Sweave is perfect for this. The only problem is that I find myself using the same R code, within my Sweave input file

I''m trying to get the Ruby DB2 bindings to compile under Windows XP. I''ve been working on this on and off over the last few days with little success. The second step, "ruby setuyp.rb setup" was generating this error message: ABORT: Could not locate DB2 libraries or headers I know I have Db2 installed correctly so I did a little digging and found that the extconf.rb

> > If you want to define an alias symbol "bar" to "foo" (which is an > extension you want to provide), one way is to create an object file that > defines "bar" and "__imp_bar" as aliases to "foo" and "__imp_foo", > respectively, and add that object file to the import library. As a result, > the import library file

Hi, I''m trtying to install postgress v0.7.9.2008.01.28 gems: C:\>gem install -v=0.7.9.2008.01.28 postgres Building native extensions. This could take a while... ERROR: While executing gem ... (Gem::Installer::ExtensionBuildError) ERROR: Failed to build gem native extension. ruby extconf.rb install -v=0.7.9.2008.01.28 postgres checking for main() in /ms/libpq.lib... no Could not

Hi, all, Please tell me about the patch and description below. https://github.com/dovecot/core/commit/5f46b863383fc94afcd2693ecae8788cb5fdd20c example-config: Use a default uncommented "namespace inbox". https://doc.dovecot.org/configuration_manual/namespace/ There's a default inbox namespace added in 10-mail.conf. If the configuration doesn't explicitly specify a

I case someone is interesed too, why it was not working: Am 14.01.19 um 20:22 schrieb Ralf Becker: > I have to reject office files for a certain domain plus notifying the > original recipient about the rejection too. > > require ["fileinto","reject","body","enotify","variables"]; > > if allof (address :contains

Hi, Thanks for pointing direction. As far, as I understand by reversing, logic, that I want to overwrite is digged into: lib/MC/MCSectionELF.cpp MCSectionELF::PrintSwitchToSection if (ShouldOmitSectionDirective(SectionName, MAI)) { OS << '\t' << getSectionName() << '\n'; return; } // otherwise print ".section" directive and then section

On Thu, Mar 15, 2012 at 11:00:54AM +0400, Konstantin Vladimirov wrote: > Hi, > > Thanks for pointing direction. As far, as I understand by reversing, > logic, that I want to overwrite is digged into: > > lib/MC/MCSectionELF.cpp > > MCSectionELF::PrintSwitchToSection > > if (ShouldOmitSectionDirective(SectionName, MAI)) { > OS << '\t'

Hi Michael, Overall patch looks good. I do have a few comments below. My main comment is please try to make the style match that used in the MCMachOStreamer more closely. I intend to refactor more functionality into the base MCObjectStreamer class, and having them use consistent idioms makes this easier; specific instances are included in the comments: -- > diff --git

Hi Shankar, On Tue, Feb 12, 2013 at 10:46 PM, Shankar Easwaran <shankare at codeaurora.org> wrote: > Author: shankare > Date: Tue Feb 12 12:46:53 2013 > New Revision: 174990 > > URL: http://llvm.org/viewvc/llvm-project?rev=174990&view=rev [...] > ELFDefinedAtom<ELFT> *createDefinedAtomAndAssignRelocations( > StringRef symbolName, StringRef

I recently examined a bug in a program, and it turned out that the customer was using the section attribute as a form of inline-assembly mechanism, with something like: __attribute__((section("sectionName\nasm\nasm\nasm"))) this was really ugly and not at all obvious where the problem originated. Is there any way of getting LLVM or CLang to validate the name used in the section