[Bro-Dev] #895: Use of &redef attribute at inappropriate times

[Bro Tracker]

#895: Use of &redef attribute at inappropriate times
----------------------+------------------------
  Reporter:  seth     |      Owner:
      Type:  Problem  |     Status:  new
  Priority:  Normal   |  Milestone:  Bro2.2
 Component:  Bro      |    Version:  git/master
Resolution:           |   Keywords:
----------------------+------------------------

Comment (by jsiwek):

 Replying to [ticket:895 seth]:
 > This should result in a parse-time error since it doesn't make any
 sense:
 >
 > {{{
 > const foobar = 10 &redef;
 > redef foobar = 20 &redef;
 > }}}

 Why is an error preferred over a no-op?  If `redef` can be used to add (or
 modify values of?) attributes, then the above is just redundant.

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