[Bro-Dev] [JIRA] (BIT-984) inconsistent scoping rules with events
Jon Siwek (JIRA)
jira at bro-tracker.atlassian.net
Mon Mar 16 12:40:01 PDT 2015
[ https://bro-tracker.atlassian.net/browse/BIT-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jon Siwek updated BIT-984:
--------------------------
Resolution: Duplicate
Status: Closed (was: Open)
Duplicate of BIT-71.
> inconsistent scoping rules with events
> --------------------------------------
>
> Key: BIT-984
> URL: https://bro-tracker.atlassian.net/browse/BIT-984
> Project: Bro Issue Tracker
> Issue Type: Problem
> Components: Bro
> Affects Versions: git/master
> Reporter: dmandelb
> Priority: Low
>
> This works as expected:
> {noformat}
> module Foo;
> event foo()
> {
> print("foo!");
> }
> event bro_init()
> {
> event foo();
> }
> {noformat}
> But this doesn't print anything:
> {noformat}
> module Foo;
> global foo: event();
> event foo()
> {
> print("foo!");
> }
> event bro_init()
> {
> event foo();
> }
> {noformat}
> This does though:
> {noformat}
> module Foo;
> global foo: event();
> event foo()
> {
> print("foo!");
> }
> event bro_init()
> {
> event Foo::foo();
> }
> {noformat}
> I think I understand how it works now, but the scoping rules seem a bit inconsistent for events versus other data types.
--
This message was sent by Atlassian JIRA
(v6.4-OD-15-055#64014)
More information about the bro-dev
mailing list