Sure, I understand that Gambit is preventing a reload of the exact same object file. But it must be doing a very simple accounting based on the name of the object file. Perhaps you can employ that newfangled high-performance file digest code that was recently shared. ;-)
Anywho, no big deal. But it's a surprise.
It's not Gambit, but the operating system that imposes this limitation. As far as I understand it, this is one reason to why Gambit compiles files into .o1 then .o2 and so on; you can load a .o1 file, recompile and then load the .o2 file.
/Per