anchor.diff:  The `YIELD` subclause may only be omitted in the standalone form of `CALL` to call a procedure that does not return any result fields.
   In this case the query will return as many (empty) rows as produced by the called procedure.
   
  -A further simplification allowed in the standalone form is to use `YIELD *` to denote that all non-deprecated result fields produced by the procedure are to be returned by the statement.
  +A further simplification allowed in the standalone form is to use `YIELD *` to denote that all non-deprecated result fields produced by the procedure implementation are returned by the statement.
   The `YIELD *` form is _only_ allowed in the standalone form of `CALL`.
   
   Different forms of standalone calls are detailed next.
  
positive.code: 
  *Author:* Stefan Plantikow <stefan.plantikow@neotechnology.com>
  *Author:* Nigel Small <nigel.small@neotechnology.com>
  *Author:* Rickard Öberg <rickard.öberg@neotechnology.com>
  
  [abstract]
  
negative.code: * Argument passing
  ** `Explicit`: Arguments are passed explicitly directly after the procedure name
  ** `Implicit`: Arguments are passed implicitly via the statement parameters
  * May return
  ** `New Fields`: This procedure call pattern may be used with procedures that may or may not return result fields.
  ** `No Fields`: This procedure call pattern is _only_ available for procedures that do not return any result fields.
  * New (variable) bindings
  ** `None`: The call yields no new variables
  ** `Given`: The call yields the given new variables in the order specified
  ** `Non-Deprecated`: The call yields all non-deprecated result fields as new variables in the order specified by the procedure's result signature
  