[Bro-Dev] Opaque type in plugin

Jan Grashöfer jan.grashoefer at gmail.com
Fri May 6 15:39:54 PDT 2016

> Took me a bit to look at this, but I've tried it now. My guess is that
> it was a namespace issue. Look at the attached patch, that version
> works for me.

Thanks a lot for taking a look! I missed that "using" does not do the
trick for a definition. I guess its time to read a C++ book :)

> That said, your version using "static" is completely fine. Indeed,
> it's even the better one for the plugin case: defining it globally
> non-static is useful only if other object files need to access it.
> Inside your plugin, that's not the case; and outside the plugin nobody
> can (because nobody can rely on the plugin being present). So I think
> your solution is just fine.

I am happy to hear that this is a proper solution. My fear was that I
was missing a mechanism, which announces the type to Bro. My thought was
that in this case the limited visibility might become an issue.

Big thanks for your support!

More information about the bro-dev mailing list