[Bro-Dev] [JIRA] (BIT-757) Change split* to return a string_vec rather string_array

scampbell (JIRA) jira at bro-tracker.atlassian.net
Mon Jan 19 09:40:01 PST 2015

    [ https://bro-tracker.atlassian.net/browse/BIT-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19500#comment-19500 ] 

scampbell commented on BIT-757:

Just wanted to upvote this ticket as the returned list from split() cause not being able to sort the results of a split so that they are in the same order as the original object is kinda maddening....

Perhaps a vsplit() bif which will return a vector rather than a list?

> Change split* to return a string_vec rather string_array
> --------------------------------------------------------
>                 Key: BIT-757
>                 URL: https://bro-tracker.atlassian.net/browse/BIT-757
>             Project: Bro Issue Tracker
>          Issue Type: Problem
>          Components: Bro
>    Affects Versions: git/master
>            Reporter: Matthias Vallentin
>              Labels: language
> Currently, `{{split}}{{ and friends return a }}{{string_array}}{{, which is a }}{{table[count] of string}}{{. However, these BiFs should return a }}{{string_vec}}{{ or }}{{vector of string}}{{ to allow for sequential iteration over the result. The problem with the current approach is not only that it is wrong modeled (the associative container does not make sense), but also that iteration over the elements, which are obviously ordered, is neither deterministic nor sequential. Presumably this mismatch exists because vectors were not available when the }}{{split*}}` functions have been created.

This message was sent by Atlassian JIRA

More information about the bro-dev mailing list