Dual ipv6 addresses not parsed correctly

[bbannier]

Looks like currently the grammar does not support parsing dual ipv6 addresses.

# x.zeek
event zeek_init()
	{
	print [2001:db8:0:0:0:FFFF:192.168.0.5];
	print [2001:db8::FFFF:192.168.0.5];
	}

$ zeek-format x.zeek
cannot parse line 3, col 8: "2001:db8:0:0:0:FFFF:"
# x.zeek
event zeek_init()
        {
        print [ 2001:db8:0:0:0:FFFF: 192.168.0.5];
        print [2001:db8::FFFF:192 .168.0.5 ];
        }

This currently produces broken output with zeek-format.

[ckreibich]

Oh yeah, good one Benjamin. The IPv6 parser is super simple and doesn't match Zeek's. I just grabbed an IPv6 regex at the time, kicking that can down the road. We should make that parser match Zeek's.

[vpax]

Here's another bug I just ran across - let me know if I should create a separate issue.

Original:

event zeek_init()
{
local site = set(0.0.0.0, 0.0.0.5, 0.0.0.128, [dada:beef::],
[dada:beef::ffff], [dada:beef::ffff:ffff],
[dada:beef::ffff:ffff:ffff],
[dada:beef::ffff:ffff:ffff:ffff]);
}

zeek-format'ed:

event zeek_init()
{
local site = set(0.0.0.0, 0.0.0.5, 0.0.0.128, [dada:beef::], [
dada:beef::ffff], [dada:beef::ffff:ffff], [
dada:beef::ffff:ffff:ffff], [dada:beef::ffff:ffff:ffff:ffff]);
}

which leads to parse errors, because Zeek requires that IPv6 addresses appear on the same line as the [ that introduces them.