Giuseppe Ragusa wrote:
Uwe,
- Where is *lexical* scoping involved?
Abuse of notation. I intended to say scoping.
- Are you really calling you code from a clean workspace?
Yes it is clean.
- Why don't use pass g through optim() to f? Please do so, because it
might be a scoping problem.
Tried
Giuseppe Ragusa wrote:
I have two machines a linux_amd64_x86 (gentoo_amd64) and a linux_x86. Both run
R-2.1.0. I have a very long program (hopefully will become a package)
that works perfectly on the linux_amd_x64. Great means no error, no
problems and results that, where the analytic solution
Uwe,
- Where is *lexical* scoping involved?
Abuse of notation. I intended to say scoping.
- Are you really calling you code from a clean workspace?
Yes it is clean.
- Why don't use pass g through optim() to f? Please do so, because it
might be a scoping problem.
Tried that. Still no luck.
Giuseppe Ragusa [EMAIL PROTECTED] writes:
I have two machines a linux_amd64_x86 (gentoo_amd64) and a
linux_x86.
You might want to try running valgrind on your code on the 32bit
machine. This may turn up a silent coding error that is manifesting
on the 64bit platform.
I think there is a new
