Anyway, I will look into alternate ways of doing this. Perhaps a routeserver specific solution is the best. It does have a method, the realization of which can be implementation specific. Method-name can have any number of arguments. Non-optional comment describes the semantics.
Methods can be names or operators.
This is a new syntax notation, of which there are many. Assume an ISP doesn't upgrade and someone else upgrades the tools. The tools propagate, and the original ISP receives an object it doesn't understand. Cengiz suggests this is to extend parse tables so they won't break. Tony Li suggested this can be handled by exception routines of parsers.