Overkill my friend... overkill. the _g versions don't change how they interact
with the outside world, only how they work internally. Class files generated
from javac and javac_g are the same. Unless you're debugging a failure of
rmiregistry there is no need for rmiregistry_g. Please send the stack. The
only thing you have to do special for working with _g is compile debuggable
versions of *your* *native* *libs*. usually a quick `ln -s libmine.so
libmine_g.so` is all it takes. -=Chris
cabbey at home dot net <*> http://members.home.net/cabbey
I want a binary interface to the brain!
Today's opto-mechanical digital interfaces are just too slow!
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
