CGAL users discussion list

[Fritz Mueller <>]

Hi Marc — thank you for the prompt reply!

>> Looking into the sources a bit, get_static_error_handler() etc. are define 
>> in header-only mode as inlines, returning references to local statics.  I 
>> think this means each call could conceivably use different storage for 
>> those statics,
> 
> No. A static variable inside a function is a unique global object. It is 
> the usual way to simulate C++17 inline variables and get singletons.

Okay, good to know this is true, even for inlines -- thanks.  I can do some 
experiments with a small bit of test code to verify that I understand 
correctly.

>> some instrumentation indicates that this is what is happening (if I log 
>> the address of _error_handler within get_standard_error_hander(), I see 
>> multiple distinct addresses during a run of my program.)
> 
> That seems very broken. I would almost suspect that you are on windows, 
> calling the function from several DLLs...

Well, OS X Catalina w/ clang 11, actually.  But my use case is somewhat 
complicated: compiling into a dylib which is being loaded as a module into 
node.js.

Thanks for the confirmation that it *should* work.  I’ll try some experiments 
with some small test programs, and also dig a little deeper to see if node/v8 
might in fact be loading more than one instantiation of my module.

> We need a testcase and details about your setup so we can reproduce the 
> issue first, as with most bugs.

I’ll make sure to have those in hand if I end up coming back around for 
another pass on this one!

        thanks again,
           —FritzM.