I have not noticed it before. I wonder why it is not recommended for anything but testing/debugging? Perhaps it slows things down in some way?
-Tom On Jan 19, 2008 4:27 AM, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote: > I just noticed this in JNA...could be new? > > setProtected > > public static void setProtected(boolean enable) > > Set whether native memory accesses are protected from invalid > accesses. This should only be set true when testing or debugging, and > should not be considered reliable or robust for multithreaded > applications. Protected mode will be automatically set if the system > property jna.protected has a value of "true" when the JNA library is > first loaded. > > If not supported by the underlying platform, this setting will have > no effect. > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > -- Blog: http://www.bloglines.com/blog/ThomasEEnebo Email: [EMAIL PROTECTED] , [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
