Re: [Rd] .Call and Segmentation Fault

2005-08-27 Thread Prof Brian Ripley
On Sat, 27 Aug 2005, Ricardo Luiz Andrade Abrantes wrote: > Hi! > Yes, I am returning a SEXP from the functions called from R, and the > problem occurs before (thousands of iterations before) the return > point. > In fact I runned valgrind into R and when I call ".Call(...) " I got > many errors l

Re: [Rd] .Call and Segmentation Fault

2005-08-27 Thread Ricardo Luiz Andrade Abrantes
Hi! Yes, I am returning a SEXP from the functions called from R, and the problem occurs before (thousands of iterations before) the return point. In fact I runned valgrind into R and when I call ".Call(...) " I got many errors like: ==4324== Use of uninitialised value of size 8 ==4324==at 0x1CB

Re: [Rd] RFC: "loop connections"

2005-08-27 Thread Gabor Grothendieck
This may not be entirely on the mark in terms of relevancy but just in case there is some relevancy I wanted to bring it up. Just to be concrete, suppose one wants to run the following as a concurrent process to R. (What is does is it implicitly sets x to zero and then for each line of stdin it

Re: [Rd] RFC: "loop connections"

2005-08-27 Thread dhinds
Martin Maechler <[EMAIL PROTECTED]> wrote: > In the mean time, I think it has become clear that > "loopconnection" isn't necessarily a better name, and that > textConnection() has been there in "the S litterature" for a > good reason and for quite a while. > Let's forget about the naming and the e

Re: [Rd] bug in L-BFGS-B? (PR#8099)

2005-08-27 Thread Prof Brian Ripley
On Sat, 27 Aug 2005, Peter Dalgaard wrote: > Prof Brian Ripley <[EMAIL PROTECTED]> writes: > >> Check your versions of MASS. The Windows one appears to be an outdated >> version, and does different things. > > Forgetting to run tools/rsync-recommended during build will do that > sort of thing to

Re: [Rd] bug in L-BFGS-B? (PR#8099)

2005-08-27 Thread Peter Dalgaard
Prof Brian Ripley <[EMAIL PROTECTED]> writes: > Check your versions of MASS. The Windows one appears to be an outdated > version, and does different things. Forgetting to run tools/rsync-recommended during build will do that sort of thing to you, but it would seem that Berwin used a binary down

Re: [Rd] bug in L-BFGS-B? (PR#8099)

2005-08-27 Thread Prof Brian Ripley
Check your versions of MASS. The Windows one appears to be an outdated version, and does different things. As for the problem, yes it probably is a bug in L-BFGS-B. Fancy debugging the code? On Sat, 27 Aug 2005 [EMAIL PROTECTED] wrote: > > --WWm7B+u2U4 > Content-Type: text/plain; charset=us-

Re: [Rd] Writing R-extensions

2005-08-27 Thread Prof Brian Ripley
On Sat, 27 Aug 2005, Berwin A Turlach wrote: > G'day all, > > After reading through "Writing R Extensions", Version 2.1.1 > (2005-06-20), I thought the the following points might need > clarifications or corrections. (I checked that these comments also > hold for "Writing R Extensions", Version 2

[Rd] bug in L-BFGS-B? (PR#8099)

2005-08-27 Thread berwin
--WWm7B+u2U4 Content-Type: text/plain; charset=us-ascii Content-Description: message body text Content-Transfer-Encoding: 7bit G'day all, I believe that this is related to PR#1717 (filed under not-reproducible) which was reported for a version of R that is a quite a bit older than the ones used

Re: [Rd] Writing R-extensions

2005-08-27 Thread Prof Brian Ripley
On Sat, 27 Aug 2005, Berwin A Turlach wrote: > G'day all, > > After reading through "Writing R Extensions", Version 2.1.1 > (2005-06-20), I thought the the following points might need > clarifications or corrections. (I checked that these comments also > hold for "Writing R Extensions", Version 2

[Rd] Writing R-extensions

2005-08-27 Thread Berwin A Turlach
G'day all, After reading through "Writing R Extensions", Version 2.1.1 (2005-06-20), I thought the the following points might need clarifications or corrections. (I checked that these comments also hold for "Writing R Extensions", Version 2.2.0.) 1) When I ran "package.skeleton" recently, I noti

Re: [Rd] wchar and wstring.

2005-08-27 Thread Prof Brian Ripley
On Fri, 26 Aug 2005, James Bullard wrote: > Hello all, I am writing an R interface to some C++ files which make use > of std::wstring classes for internationalization. Previously (when I > wanted to make R strings from C++ std::strings), I would do something > like this to construct a string in R

Re: [Rd] Memory leakage/violation?

2005-08-27 Thread Henrik Bengtsson
And... hopefully my final admission that I did not do my background research; the system I'm working with and borrowed from a colleague (since my own is on service) is not a Windows XP Pro _SP2_, but apparently _SP1_. It's not worth troubleshooting much until I get an update here. Thank you B

Re: [Rd] Memory leakage/violation?

2005-08-27 Thread Henrik Bengtsson
Prof Brian Ripley wrote: > On Sat, 27 Aug 2005, Uwe Ligges wrote: > >> Thomas Lumley wrote: >> >>> I can't reproduce this on R2.2.0dev on Windows XP (in a few hundred >>> tries), or running under Valgrind on AMD64 Linux (in four or five >>> tries). >> >> >> Cannot reproduce either (using R-2.1.1

Re: [Rd] RFC: "loop connections"

2005-08-27 Thread Martin Maechler
> "David" == David Hinds <[EMAIL PROTECTED]> > on Mon, 22 Aug 2005 23:34:15 + (UTC) writes: David> I've just implemented a generalization of R's text connections, to David> also support reading/writing raw binary data. There is very little David> new code to speak of.

Re: [Rd] RFC: "loop connections"

2005-08-27 Thread David Hinds
On Sat, Aug 27, 2005 at 09:23:37AM +0100, Prof Brian Ripley wrote: > > >"loop" is short for "loopback". A loop or loopback device is one that > >just returns the data sent to it. > > That is definitely not what text connections do, and not what I read the > proposal as being given the analogies

Re: [Rd] Memory leakage/violation?

2005-08-27 Thread Henrik Bengtsson
Thank you Thomas and Uwe for this. This is really odd, because today I can neither reproduce it myself (I rebooted my computer this morning). I try to recall what I did yesterday: I did _not_ reboot my machine, but I did install the latest binaries of R 2.1.1 and 2.2.0dev from CRAN. I did cl

Re: [Rd] Memory leakage/violation?

2005-08-27 Thread Prof Brian Ripley
On Sat, 27 Aug 2005, Uwe Ligges wrote: > Thomas Lumley wrote: >> I can't reproduce this on R2.2.0dev on Windows XP (in a few hundred >> tries), or running under Valgrind on AMD64 Linux (in four or five tries). > > Cannot reproduce either (using R-2.1.1 and an older version of R-devel, > though). M

Re: [Rd] Memory leakage/violation?

2005-08-27 Thread Uwe Ligges
Thomas Lumley wrote: > I can't reproduce this on R2.2.0dev on Windows XP (in a few hundred > tries), or running under Valgrind on AMD64 Linux (in four or five tries). Cannot reproduce either (using R-2.1.1 and an older version of R-devel, though). Maybe a compiler issue? Henrik, do you use exact

Re: [Rd] Free-form to fixed-form Fortran

2005-08-27 Thread Prof Brian Ripley
On Sat, 27 Aug 2005, Ales Ziberna wrote: > Thank you for your reply! > > I know I can use g77 with -ffree-form. However, I do not know how to make a > package so that when others would build a package, these subrutines would > compile with "-ffree-form". I heard of "makevars" and flags, however I

Re: [Rd] Free-form to fixed-form Fortran

2005-08-27 Thread Ales Ziberna
Thank you for your reply! I know I can use g77 with -ffree-form. However, I do not know how to make a package so that when others would build a package, these subrutines would compile with "-ffree-form". I heard of "makevars" and flags, however I read on the mailing list archives that they are

Re: [Rd] RFC: "loop connections"

2005-08-27 Thread Prof Brian Ripley
On Sat, 27 Aug 2005 [EMAIL PROTECTED] wrote: > Gabor Grothendieck <[EMAIL PROTECTED]> wrote: >> OK. I guess you want one of the core people to respond but in the One has. >> interim can you explain the terminology "loop"? >> Also, do you have any prototypical applications in mind? > > "loop" is