that is, the keyword arguments come after the system name (as you'd expect for a normal CL function).
Note that all those arguments get swept up into the :original-initargs slot of the test-op instance, and then propagated through dependent ops.
What this means is that :original-initargs can be used as an arbitrary property list on which to stash attributes that will modulate the performance of any ASDF operation.
I have used this for a number of extensions to asdf operation classes.
This would actually be
(asdf:oos 'asdf:doc-op <target- system- name> :target-dir ...)
that is, the keyword arguments come after the system name (as you'd expect for a normal CL function).
Note that all those arguments get swept up into the :original-initargs slot of the test-op instance, and then propagated through dependent ops.
What this means is that :original-initargs can be used as an arbitrary property list on which to stash attributes that will modulate the performance of any ASDF operation.
I have used this for a number of extensions to asdf operation classes.