anchor.diff:  }
   ----
   
  -This may also be useful for applications that need a custom type converter but want to use the static convenience methods (`populateCommand`, `run`, `call`). The `converter` annotation does not require a `CommandLine` instance so it can be used with the static convenience methods.
  +This may also be useful for applications that need a custom type converter but want to use the static convenience methods (`populateCommand`, `run`, `call`, `invoke`). The `converter` annotation does not require a `CommandLine` instance so it can be used with the static convenience methods.
   
   Type converters declared with the `converter` attribute need to have a public no-argument constructor to be instantiated, unless a <<Custom Factory>> is installed to instantiate classes.
   
  
positive.code: 
  * `CommandLine::call`
  * `CommandLine::run`
  * `CommandLine::parseWithHandler` (with the built-in `Run...` handlers)
  * `CommandLine::parseWithHandlers` (with the built-in `Run...` handlers)
  
  
negative.code: 
  
  === Stdout or Stderr
  From picocli v3.0, the `run`, `call` and `invoke` convenience methods follow unix conventions:
  print to stdout when the user requested help, and print to stderr when the input was invalid or an unexpected error occurred.
  
  Custom handlers can extend `AbstractHandler` to facilitate following this convention.
  