Skip to content

Commit

Permalink
Further explanation of on-abnormal-exit of call-with-input-process
Browse files Browse the repository at this point in the history
Not only the default, but the valid arguments differ.
In retrospect, we should probably use different argument name
than do-process.  Oh well.
  • Loading branch information
shirok committed Dec 15, 2023
1 parent 0b351b9 commit e1f5580
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions doc/modgauche.texi
Original file line number Diff line number Diff line change
Expand Up @@ -18343,6 +18343,10 @@ for non-zero exit status. If it is a procedure, it is called with
a process object; when the procedure returns, @code{call-with-input-process}
returns normally.

Note that @var{on-abnormal-exit} differs from @code{do-process}
(@pxref{Running subprocess}). We want finer control over the situation
than merely check if the subprocess is succeeded or failed.

The semantics of @var{command} and other keyword arguments are the same
as @code{open-input-process-port} above.
@c JP
Expand All @@ -18363,6 +18367,10 @@ as @code{open-input-process-port} above.
子プロセスオブジェクトを引数にしてその手続きが呼ばれます。その手続きが
戻れば、@code{call-with-input-process}は正常動作と同じように戻ります。

@var{on-abnormal-exit}の意味が@code{do-process}とは異なることに注意してください
(@ref{Running subprocess}参照)。この手続きを使う場合は、
単にサブプロセスの成功/失敗を知るだけでなく、より細かな制御を必要とする場合が多いからです。

@var{command}および他のキーワード引数の意味は@code{open-input-process-port}と
同じです。
@c COMMON
Expand Down

0 comments on commit e1f5580

Please sign in to comment.