AttachCurrentThread() in an already-attached thread harmless?

To work with various APIs, it's sometimes convenient (or necessary) not to pass around the JNIEnv argument all over the place. If I call some function that's running in the same thread and that function calls AttachCurrentThread() to get the current JNIEnv pointer, is that (a) harmless, (b) inexpensive, especially in loops (i.e., basically a no-op since the current thread is already attached)?

- Paul

[418 byte] By [pauljlucasa] at [2007-10-3 9:43:55]