Jan:
> Event handlers just don't seem to inherit the surrounding module
> namespace, which kind of makes sense if you want to handle events
> generated in the global namespace.
I agree that it does make sense in that regard. It's certainly prudent
- as mentioned - to always qualify your events. Th
On Thu, Sep 27, 2018 at 3:47 AM Matthias Vallentin wrote:
> I hope this illustrates the issue a bit better.
Thanks, that helps. Underlying issue/pitfall still seems related to
module interactions with event handler definition/declaration, so
added a link back from [#163]. Namely, seems you can
On 27/09/2018 10:47, Matthias Vallentin wrote:
> If I remove the event declaration, I get:
>
> error in ./foo.bro, line 10: not an event (Foo::foo())
The following works for me:
module Foo;
event Foo::foo()
{
print "foo";
}
event bro_init()
{
>It might also help if you send actual examples that can be run if that
>still doesn't work because it's hard to interpret what you mean by
>"publish via Broker".
Okay, so first a pure Bro example. This one works:
module Foo;
global foo: event(); // declaration
event foo()
{
