[Bro-Dev] #675: enum values in log output can be ambitious

[Bro Tracker]

#675: enum values in log output can be ambitious
---------------------+--------------------
 Reporter:  robin    |      Owner:
     Type:  Problem  |     Status:  new
 Priority:  Normal   |  Milestone:  Bro2.0
Component:  Bro      |    Version:
 Keywords:           |
---------------------+--------------------
 Assume code like this extending enums:

 {{{
    module M1;

    redef enum Other::MyEnum += { green };

    module M2;


    redef enum Other::MyEnum += { green };
 }}}

 That generates two separate enum labels internally, but the in the log
 output both appear as `green`. Normally it probably won't matter much, but
 now reading it back via the input framework is ambitious,

 Not sure what the best solution is. I'm thinking to leave everything as it
 is except when we actually do have such ambiguous labels: in that case, we
 could write out the fully scoped `M1::green`.

-- 
Ticket URL: <http://tracker.bro-ids.org/bro/ticket/675>
Bro Tracker <http://tracker.bro-ids.org/bro>
Bro Issue Tracker