From amredd at gmail.com  Fri Nov 12 22:26:24 2010
From: amredd at gmail.com (Andrew Redd)
Date: Fri, 12 Nov 2010 14:26:24 -0700
Subject: [Rd] unloading compiled code.
Message-ID: <AANLkTimR+c8r=gBPKb9-EFcUr-wCVeS6+EJSNXBH3zHz@mail.gmail.com>

I have a package that I'm developing that I need to unload the
library.  Long story short I figured out that the leaving the compiled
code loaded lead to a segmentation fault, but unloading the code will
fix it.  I've read the documentation and it appears that there are
several ways to do this?  What is the popper accepted current standard
for unloading compiled code?

The options as I understand them are:
1. dyn.unload
2. library.dynam.unload
used with either
A. .Last.lib
B. .onUnload

If it makes a difference my package does use a NAMESPACE so the
package is loaded through useDynLib.

Thanks,
Andrew Redd



[Rd] unloading compiled code.
Andrew Redd