When parsing CompileCommand, `MethodMatcher::parse_method_pattern()` gets handed the full trailing line after the command name, consisting of method name, optionally with signature, and an optional trailing option separated by comma from the name.

One of its first actions is to canonicalize the string (e.g. replacing colons with blanks).

It does this over the full line. Therefore it destroys the option string if the option happens to contain colons. It also replaces dots with '/'.

There is special handling for floating point values to deal with the overwritten dots. Other than that, using these characters in option values won't work. It would be nice to modify the matcher to not touch the option string, instead.