Some still don't pass:
- events-ssl doesn't work; not clear yet why, there may be some
problem with SSL connections.
- broccoli needs the changes topic/jsiwek/64bit-val-fix, plus
adaption of the protocol version.
- pybroccoli crashes even with the 64bit-val-fix changes. Reason
unclear.
This includes flex/bison/binpac/bifcl input files as well as C/C++ header
files. Header files for the bro target are determined dynamically at
configure time from a given list of source files.
This addresses #413.
The CMake-generated config.h would redundantly define some types to
themselves, causing lots of warning in some cases (e.g. Xcode build).
This addresses #414
* Logging activity is currently focused on messages.
* Does command oriented logging still make sense for SMTP?
* Remaining (known) weak points:
* Poor handling of wrapped message headers.
* Poor separation into various scripts by functionality.
* base.bro will likely include nothing after 'DATA'.
* Out of order command/response pairs are not supported yet.
The customization point is provided between the time a file
to be extracted has it's file handled opened and when the first
chunk of data is written to disk.
* Multiple pipelined requests before any replies is now supported.
* HTTP::build_url function that takes a connection and builds a
url current request/response pair.
* I left in an example to show a likely bug with the record
extension mechanism.
the random number generator.
This works like the corresponding command line option but is more
convinient when writing tests as it can be set in btest.cfg.
with the field.
This works now:
type X: record {
a: table[string] of bool &default=table( ["foo"] = T );
b: table[string] of bool &default=table();
c: set[string] &default=set("A", "B", "C");
d: set[string] &default=set();
};
I think previously the intend was to associate &default with the
table/set (i.e., define the default value for non-existing indices).
However, that was already not working: the error checking was
reporting type mismatches. So, this shouldn't break anything and make
things more consistent.
For a bro script that is documented like:
## ...
## bar: ...
## Returns: ...
global foo(bar: string): string;
the generated reST documentation will automatically substitute meaningful
markup (reST field lists) for the parameter and return type comments
