On Sat, Dec 22, 2018 at 04:44:14PM -0500, Daniel Jakots wrote: > Here's a diff that change the delimiter to ":". This breaks existing > scripts but it would make the syntax like pf.conf instead of using > another symbol for a port range. Changing it to double-colon for sanity and consistency seems good, but maybe that's too much of a break at once? Or are ranges not considered critical enough to worry about this? I never use them.
> If you have a better idea how to solve this problem, please share! Perhaps phasing this out by first accepting both as delimiter, then dropping the dash later on? One alternative would be to try the given word as is first, only interpreting it as a range when it's not a valid service name. Also, how do other netcat implementations handle ranges? Do we care about consistency with these?
