similar to: R-beta: installing new packages in window95 version of R

Just a short reminder / question -- We've had one posting >> Date: Sun, 17 Aug 1997 19:51:20 -0700 >> From: Kung-Sik Chan <kchan@stat.uiowa.edu> >> To: r-help@stat.math.ethz.ch >> Subject: R-beta: bug report with a predict.default that would "work" with (some) lm objects, and I think it was said that predict.lm "is being" written (Peter

I ran a function called BoxCox, taken from the book by Venables and Ripley, for checking the need for power transformation. This function works fine using the version 0.50 of R, but gives an error message with version 0.60. The lm function in version 0.60 is different from that in version 0.50. Is there a bug in the new lm function? Kung-Sik Chan >

The following seems to be a bug when I tried to use the predict function. > forbes boil.pt pressure log.pressure [1,] 194.5 20.79 303.4472 [2,] 194.3 20.79 303.4472 [3,] 197.9 22.40 310.9061 [4,] 198.4 22.67 312.1042 [5,] 199.4 23.15 314.1995 [6,] 199.9 23.35 315.0597 [7,] 200.9 23.89 317.3460 [8,] 201.1 23.99

On 1/22/17, Dave Yeo <dave.r.yeo at gmail.com> wrote: > On 01/22/17 09:57 AM, Ozkan Sezer wrote: >> On 1/22/17, Dave Yeo <dave.r.yeo at gmail.com> wrote: >>> On 01/22/17 05:35 AM, Ozkan Sezer wrote: >>>> The attached set of patches adds support for OS/2 using Watcom compiler >>>> (tested with Open Watcom 1.9). My only interest was building a

On 01/22/17 05:35 AM, Ozkan Sezer wrote: > The attached set of patches adds support for OS/2 using Watcom compiler > (tested with Open Watcom 1.9). My only interest was building a working > dll (the last patch in the set adds a makefile for it), therefore I did > not touch other places: If there is interest, I can do so. Most of the patches can have s/__EMX__/__OS2__/ excepting the

I'm having trouble with R on NT. Sept 1 97 version 50 in file rsept works fine, except I can't boost the memory - either with the menu or with DOS command Rsept -v50 In fact, if I run in DOS command mode (no shortcut) I get NT error window: errno 1411. But then R runs. With rseptbeta and rsept31 versions, R starts for a millisecond and then disappears. I've tried replacing the

Hello, as usual for me with precompiled libraries, the ones of the vorbis- sdk didn't work for me in WATCOM/Win32, so i compiled them on my own (vorbis_static.lib / vorbisfile_static.lib - it was possible after some slight changes like slightly modifiyng the typedef types that Watcom didn't know) The libraries work fine so far (like getting the file info), but when calling ov_read

I'm switching from OpenLDAP to the newly released Fedora Directory Server (formely known as the Netscape Directory Server) as a LDAP backend for my Samba domain. I'm now faced with a problem regarding how Fedora DS handles the userPassword field. Unlike OpenLDAP it encodes it in base64 so instead of reading userPassword: {SSHA}0lP+r3Z1NVan7Caf4CG9oSgnTbQRrv/p it reads: userPassword::

Hey Scott, On Wed, Apr 24, 2013 at 1:40 PM, Scott Pakin <pakin at lanl.gov> wrote: ... > > Is there some semantic reason that the increments aren't allowed to be > combined, or is this a missed optimization opportunity in LLVM? > > I believe that the wildcard is the extern keyword. Since the external symbol isn't resolved until link time, I suspect that it would be

The attached set of patches adds support for OS/2 using Watcom compiler (tested with Open Watcom 1.9). My only interest was building a working dll (the last patch in the set adds a makefile for it), therefore I did not touch other places: If there is interest, I can do so. Regards. -- O.S. -------------- next part -------------- A non-text attachment was scrubbed... Name:

We''ve all seen the job listings. We know what they''re looking for. Rockstars. Code Monkeys. Rails Ninjas. And you''re left thinking, "But I''m just a programmer." Well, not anymore. Today, you become a Rails Kung-Fu Master! "Not me," you say. "I''ve already tried using all the acts_as_something plugins and all the something_fu

On 4/24/2013 1:35 PM, Cameron McInally wrote: > > I believe that the wildcard is the extern keyword. > > Since the external symbol isn't resolved until link time, I suspect that > it would be a legal C program to do something like (maybe the language > lawyers know better though): > > XXX> cat test.c > extern int x; > > int kung( ) { > return x; > }

On Thu, 14 Dec 2000 10:06:39 +1100, Michael Smith wrote: >>I've done a port for OS/2 using Watcom C++, including a simple command line >>player based on vorbisfile_example.c, which can be downloaded from >>http://silk.apana.org.au/utils.html >>It'd be nice if my changes could be commited to CVS, should I just post >>patches here? > >Yes, unless

On Tue, Jun 30, 2015 at 12:30:35PM -0700, Eric Lindblad wrote: > I don't know if it would be of any use - and I know that > the configure script searches for gawk, sed and grep - > but Watcom has free 32 and 64 bit compilers, and > the msvc files for Xapian no longer appear to be > maintained, so perhaps Xapian build files written for > [Open] Watcom could be made, as such

I have a query after finding an error running Rtools on a Windows machine. I am trying to build an update to the R fda library using Rtools27 under Windows XP Pro. This is the current fda library on RForge: http://r-forge.r-project.org/projects/fda Following R CMD build, R CMD check produces the following error in 00Install.out: installing R.css in F:/work/RForge/fda.Rcheck make: ***

Has anyone ever successfully used Fortran character strings with R? ?Foreign says R C Fortran integer int * integer .... character char ** [compiler dependent] Character strings are passed as C arrays of character strings to Fortran: the first string may be usable if its length is passed

Hello. I am trying to use a FORTRAN subroutine from within R (Windows version). This fortran subroutine is compiled using the Open Watcom Fortran compiler and the compiled object file is called ritscale.obj. Following the explanation on pages 193-194 of "The New S language" I use the dyn.load command: > dyn.load("f:/maxent/ritscale.obj") Error in dyn.load(x,

I have just downloaded rsept.zip and rseptbeta.zip for Windows 95 and I think that is a GREAT product. 1st: I want to know the differences between them. 2nd: I'm interested very much in time series analysis, but watching the html help there is not any function (for ex. like the S-Plus functions acf pacf and arima functions etc). If there is some pacages to plug-in with documentation

I have just downloaded rsept.zip and rseptbeta.zip for Windows 95 and I think that is a GREAT product. 1st: I want to know the differences between them. 2nd: I'm interested very much in time series analysis, but watching the html help there is not any function (for ex. like the S-Plus functions acf pacf and arima functions etc). If there is some pacages to plug-in with documentation

A colleague is using Watcom F77 version 11 in Windows NT, and wants to create DLLs callable from R. (He was previously able to do external calls from S-PLUS). Does anyone know what magic is necessary so that it uses the right calling convention? In a debugger, it appears it's using a register-based calling convention, no matter what we ask for, but we're probably asking in the wrong