From 6f92d92e7b1b6a620f1ddd4bcfb080732cae3649 Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Tue, 25 May 2021 12:58:25 -0700 Subject: don't recommend RUN over MRUN in general Signed-off-by: Sean Whitton --- src/connection.lisp | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) (limited to 'src/connection.lisp') diff --git a/src/connection.lisp b/src/connection.lisp index 9af1f86..3f979d2 100644 --- a/src/connection.lisp +++ b/src/connection.lisp @@ -418,9 +418,12 @@ Some (but not all) connection types will want to use this when implementing ESTABLISH-CONNECTION, CONNECTION-RUN, CONNECTION-WRITEFILE etc. to avoid the overhead of splitting the output streams only to immediately recombine them. -Some :POSIX properties which want to run a lot of commands and don't need to -separate the streams might want to use this too, but usually it is best to -start with RUN." +Code in property definitions which will not examine command output should +usually use this in preference to RUN for a performance boost; an exception is +when the command sends a lot of text to stdout which might make it harder for +the user to pick out error messages. Code which examines command output +should use RUN and only examine the stream from which the output to be read is +expected." (%process-run-args (informat 4 "~&MRUN ~A" cmd) (multiple-value-bind (out exit) -- cgit v1.2.3