On Thu, Mar 08, 2018 at 13:28 -0600, you wrote:
> * Rename "proxy" nodes? "compute" maybe? > (1) &synchronized, &mergeable, &persistent. Seems fine to deprecate these > now. Agree. > (2) Communication framework scripts. It's awkward to deprecate stuff > here since they internally will be using what is deprecated. I think > it makes sense to just remove it and let users manually make a copy if > they still need it. Likewise agree. > (3) Old C++ comm. code, e.g. RemoteSerializer. I think we'll leave > this untouched for the 2.6 release? Yep, I'm looking forward to ripping that out for 2.7. :) > (4) BIFs associated with old comm. system. Depends on (3) (and also > actually (2)), though if the internal core code remains, I think it > makes sense to add &deprecated to these. Deprecating them sounds good. > It makes more sense to me to assume the user wants to insert the key > with a sane default value (e.g. zero/empty) in those cases, otherwise, > it's awkward/race-prone to require they do it themselves. Agree with this as well, has always felt a bit awkward to me too. Robin -- Robin Sommer * ICSI/LBNL * ro...@icir.org * www.icir.org/robin _______________________________________________ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev