On Thu, Sep 27, 2018 at 3:47 AM Matthias Vallentin <vallen...@icir.org> 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 try to reason about events + modules by trying to remember that event declarations will implicitly get prefixed by module names while event handlers don't (i.e. a handler for something that hasn't been declared yet isn't considered an implicit declaration... or at least not the same kind of declaration). It's not in the scope of Bro 2.6 to try improving anything here, so I still suggest the simplest rule/approach to remember is to always/everywhere prefix event names with an intended module name. - Jon [#163] https://github.com/bro/bro/issues/163 _______________________________________________ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
