From edd at debian.org  Sat Jan 31 17:15:40 2009
From: edd at debian.org (Dirk Eddelbuettel)
Date: Sat, 31 Jan 2009 10:15:40 -0600
Subject: [Rd] Side-effects of require() vs library() on x86_64 aka amd64
In-Reply-To: <49847459.4060109@biostat.ku.dk>
References: <18817.12266.512527.675087@ron.nulle.part>
	<18819.54749.999186.155947@ron.nulle.part>
	<20090131145913.GI248@ziti.local>
	<18820.28545.87207.417437@ron.nulle.part>
	<49847459.4060109@biostat.ku.dk>
Message-ID: <18820.31020.62883.201251@ron.nulle.part>


Hi Peter,

On 31 January 2009 at 16:55, Peter Dalgaard wrote:
| Not really (and you know where to find the sources...).

Yes, and I had dug through that in the past for littler and other embedding
work.  I was just wondering if I had missed any documentation, besides the
few lines about --slave from the help page, --help switch and intro manual.

| But sometimes it 
| only takes one memory allocation more or less to shift the effect of a 
| memory bug to a completely different point in space an time.

That seems to have been the case. It also didn't help that x86 didn't trigger
it, or I would have noticed sooner after my 0.1.0 release.  Building on
different architectures help shaking these things out.

Dirk

-- 
Three out of two people have difficulties with fractions.



[Rd] Side-effects of require() vs library() on x86_64 aka amd64
Dirk Eddelbuettel