I was thinking of just a simple Weird::Type enum with comments, much like
how the Notice documentation is generated. I do also like the thought of
the structured namespace.
Maybe more generally, we should to make a Weird closer to a Notice. For
example, if a file analyzer generates a weird, there are no fields in the
weird.log to map it back to the offending file. I realize that that's
trickier, since Weirds can be generated from either the core or script-land.
--Vlad
On Fri, Jun 27, 2014 at 5:54 PM, Robin Sommer wrote:
>
>
> On Fri, Jun 27, 2014 at 21:41 +, you wrote:
>
> > A suggestion would be to change weirds to use an enum instead of a
> > string value.
>
> Yeah, either that, or introducing a structured ID namespace (e.g.,
> "http.client.unexpected_data"), potentially with some static analysis
> to find IDs that aren't linked to docs.
>
> In either case it would be nice if the scheme unified reporting weirds
> from core and script land.
>
> Robin
>
> --
> Robin Sommer * Phone +1 (510) 722-6541 * ro...@icir.org
> ICSI/LBNL* Fax +1 (510) 666-2956 * www.icir.org/robin
>
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
