Allow glog to be queried as to whether or not InitGoogleLogging has been called.

[KevinLucidyne]

If you call InitGoogleLogging twice, then you get a fatal error and the program ends.

However, there is no way to query glog as to whether glog has already been initialized or not. This query is in the glog code (obviously) but it's not exposed in the API. Please make this public.

Here is the use case where this is useful, for me at least.

I'm adding an unmanaged C++ package that uses glog to a managed C# DLL that is in turn dynamically loaded to a C# managed code application but I need to change the glog default behavior. I can't call InitGoogleLogging in the application so instead I have to do the initialization in a nested singleton class in the DLL.

[concretevitamin]

+1!

[konstan]

+1!

[debamax]

+1! 🙏

[OasisArtisan]

This is still an issue but with a fairly easy work around. (Unless I'm missing something obvious)

We just need access to
bool IsGoogleLoggingInitialized();
Which is defined in the glog/src/utilities.h

So just define the following in your own code.

namespace google {
  namespace glog_internal_namespace_ {
    extern bool IsGoogleLoggingInitialized();
  }
  const auto& IsGoogleLoggingInitialized = glog_internal_namespace_::IsGoogleLoggingInitialized;
}

The linker should take care of linking the symbol to its implementation in glog.

So now you can simply use the function as google::IsGoogleLoggingInitialized()

Cheers.

[xkszltl]

@sergiud
So how's the issue closed in 0.5?
Even worse, seems the ::google::glog_internal_namespace_::IsGoogleLoggingInitialized() is now a hidden symbol, the redecl hack won't work any more.

[sergiud]

The issue received no activity, hence I closed it. You're welcome provide a PR.

Internal declarations are not part of the API and thus can change anytime. Complaining about changes to the internals is not helpful anyway.

[xkszltl]

I think this issue is not about complaining change of internal API, but about why it is internal, because without it there's simply no reliable way to init without full control of process lifespan.
How about we simply alias it to a public API?

[sergiud]

Sure, go ahead.