[Bro-Dev] #754: Complete implementation of switch statement

[Bro Tracker]

#754: Complete implementation of switch statement
----------------------------+------------------------
  Reporter:  seth           |      Owner:  robin
      Type:  Merge Request  |     Status:  closed
  Priority:  Normal         |  Milestone:  Bro2.2
 Component:  Bro            |    Version:  git/master
Resolution:  fixed          |   Keywords:  language
----------------------------+------------------------

Comment (by jsiwek):

 Replying to [comment:7 vern]:
 > I do believe in a general rule of don't-add-features-without-a-specific-
 need, so if this isn't a motivated addition, I'd put it on hold.  (I.e.,
 okay to keep the current code in place, but don't turn it on until we find
 we need it - and then first analyze just what we really need.)

 It doesn't solve a specific/immediate problem, but the addition of a
 switch statement isn't entirely unmotivated.  I know several times I've
 been writing a script and thought "a switch (C-style, constant case
 labels) makes sense here because the structure of it makes it easier to
 reason about the logic than a large sequence of conditionals" but then I
 find/remember there is no switch statement.  I'm guessing that situation
 nags at other people, too?  Anyone have opinions on whether to disable it
 for now, or if they have a use for non-constant case label expressions?

-- 
Ticket URL: <http://tracker.bro-ids.org/bro/ticket/754#comment:8>
Bro Tracker <http://tracker.bro-ids.org/bro>
Bro Issue Tracker