-
Notifications
You must be signed in to change notification settings - Fork 181
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
system: subprocessing interface (#911)
- Loading branch information
Showing
22 changed files
with
2,291 additions
and
39 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,337 @@ | ||
--- | ||
title: system | ||
--- | ||
|
||
# System and sub-processing module | ||
|
||
The `stdlib_system` module provides interface for interacting with external processes, enabling the execution | ||
and monitoring of system commands or applications directly from Fortran. | ||
|
||
[TOC] | ||
|
||
## `run` - Execute an external process synchronously | ||
|
||
### Status | ||
|
||
Experimental | ||
|
||
### Description | ||
|
||
The `run` interface allows execution of external processes using a single command string or a list of arguments. | ||
Processes run synchronously, meaning execution is blocked until the process finishes. | ||
Optional arguments enable the collection of standard output and error streams, as well as sending input via standard input. | ||
Additionally, a callback function can be specified to execute upon process completion, optionally receiving a user-defined payload. | ||
|
||
### Syntax | ||
|
||
`process = ` [[stdlib_subprocess(module):run(interface)]] `(args [, stdin] [, want_stdout] [, want_stderr] [, callback] [, payload])` | ||
|
||
### Arguments | ||
|
||
`args`: Shall be a `character(*)` string (for command-line execution) or a `character(*), dimension(:)` array (for argument-based execution). It specifies the command and arguments to execute. This is an `intent(in)` argument. | ||
|
||
`stdin` (optional): Shall be a `character(*)` value containing input to send to the process via standard input (pipe). This is an `intent(in)` argument. | ||
|
||
`want_stdout` (optional): Shall be a `logical` flag. If `.true.`, the standard output of the process will be captured; if `.false.` (default), it will be lost. This is an `intent(in)` argument. | ||
|
||
`want_stderr` (optional): Shall be a `logical` flag. If `.true.`, the standard error output of the process will be captured. If `.false.` (default), it will be lost. This is an `intent(in)` argument. | ||
|
||
`callback` (optional): Shall be a procedure conforming to the `process_callback` interface. If present, this function will be called upon process completion with the process ID, exit state, and optionally collected standard input, output, and error streams. This is an `intent(in)` argument. | ||
|
||
`payload` (optional): Shall be a generic (`class(*)`) scalar that will be passed to the callback function upon process completion. It allows users to associate custom data with the process execution. This is an `intent(inout), target` argument. | ||
|
||
### Return Value | ||
|
||
Returns an object of type `process_type` that contains information about the state of the created process. | ||
|
||
### Example | ||
|
||
```fortran | ||
! Example usage with command line or list of arguments | ||
type(process_type) :: p | ||
! Run a simple command line synchronously | ||
p = run("echo 'Hello, world!'", want_stdout=.true.) | ||
``` | ||
|
||
## `runasync` - Execute an external process asynchronously | ||
|
||
### Status | ||
|
||
Experimental | ||
|
||
### Description | ||
|
||
The `runasync` interface allows execution of external processes using a single command string or a list of arguments. | ||
Processes are run asynchronously (non-blocking), meaning execution does not wait for the process to finish. | ||
Optional arguments enable the collection of standard output and error streams, as well as sending input via standard input. | ||
Additionally, a callback function can be specified to execute upon process completion, optionally receiving a user-defined payload. | ||
|
||
### Syntax | ||
|
||
`process = ` [[stdlib_subprocess(module):runasync(interface)]] `(args [, stdin] [, want_stdout] [, want_stderr] [, callback] [, payload])` | ||
|
||
### Arguments | ||
|
||
`args`: Shall be a `character(*)` string (for command-line execution) or a `character(*), dimension(:)` array (for argument-based execution). It specifies the command and arguments to execute. This is an `intent(in)` argument. | ||
|
||
`stdin` (optional): Shall be a `character(*)` value containing input to send to the process via standard input (pipe). This is an `intent(in)` argument. | ||
|
||
`want_stdout` (optional): Shall be a `logical` flag. If `.true.`, the standard output of the process will be captured; if `.false.` (default), it will be lost. This is an `intent(in)` argument. | ||
|
||
`want_stderr` (optional): Shall be a `logical` flag. If `.true.`, the standard error output of the process will be captured. Default: `.false.`. This is an `intent(in)` argument. | ||
|
||
`callback` (optional): Shall be a procedure conforming to the `process_callback` interface. If present, this function will be called upon process completion with the process ID, exit state, and optionally collected standard input, output, and error streams. This is an `intent(in)` argument. | ||
|
||
`payload` (optional): Shall be a generic (`class(*)`) scalar that will be passed to the callback function upon process completion. It allows users to associate custom data with the process execution. This is an `intent(inout), target` argument. | ||
|
||
### Return Value | ||
|
||
Returns an object of type `process_type` that contains information about the state of the created process. | ||
|
||
### Example | ||
|
||
```fortran | ||
{!example/system/example_process_1.f90!} | ||
``` | ||
|
||
## `is_running` - Check if a process is still running | ||
|
||
### Status | ||
|
||
Experimental | ||
|
||
### Description | ||
|
||
The `is_running` interface provides a method to check if an external process is still running. | ||
This is useful for monitoring the status of asynchronous processes created with the `run` interface. | ||
|
||
### Syntax | ||
|
||
`status = ` [[stdlib_subprocess(module):is_running(interface)]] `(process)` | ||
|
||
### Arguments | ||
|
||
`process`: Shall be a `type(process_type)` object representing the external process to check. This is an `intent(inout)` argument. | ||
|
||
|
||
### Return Value | ||
|
||
Returns a `logical` value: `.true.` if the process is still running, or `.false.` if the process has terminated. | ||
After a call to `is_running`, the `type(process_type)` structure is also updated to the latest process state. | ||
|
||
### Example | ||
|
||
```fortran | ||
{!example/system/example_process_2.f90!} | ||
``` | ||
|
||
## `is_completed` - Check if a process has completed execution | ||
|
||
### Status | ||
|
||
Experimental | ||
|
||
### Description | ||
|
||
The `is_completed` interface provides a method to check if an external process has finished execution. | ||
This is useful for determining whether asynchronous processes created with the `run` interface have terminated. | ||
|
||
### Syntax | ||
|
||
`status = ` [[stdlib_subprocess(module):is_completed(interface)]] `(process)` | ||
|
||
### Arguments | ||
|
||
`process`: Shall be a `type(process_type)` object representing the external process to check. This is an `intent(inout)` argument. | ||
|
||
### Return Value | ||
|
||
Returns a `logical` value: | ||
- `.true.` if the process has completed. | ||
- `.false.` if the process is still running. | ||
|
||
After a call to `is_completed`, the `type(process_type)` structure is updated to reflect the latest process state. | ||
|
||
### Example | ||
|
||
```fortran | ||
{!example/system/example_process_1.f90!} | ||
``` | ||
|
||
## `elapsed` - Return process lifetime in seconds | ||
|
||
### Status | ||
|
||
Experimental | ||
|
||
### Description | ||
|
||
The `elapsed` interface provides a method to calculate the total time that has elapsed since a process was started. | ||
This is useful for tracking the duration of an external process or for performance monitoring purposes. | ||
|
||
The result is a real value representing the elapsed time in seconds, measured from the time the process was created. | ||
|
||
### Syntax | ||
|
||
`delta_t = ` [[stdlib_subprocess(module):elapsed(subroutine)]] `(process)` | ||
|
||
### Arguments | ||
|
||
`process`: Shall be a `type(process_type)` object representing the external process. It is an `intent(in)` argument. | ||
|
||
### Return Value | ||
|
||
Returns a `real(real64)` value that represents the elapsed time (in seconds) since the process was started. | ||
If the process is still running, the value returned is the time elapsed until the call to this function. | ||
Otherwise, the total process duration from creation until completion is returned. | ||
|
||
### Example | ||
|
||
```fortran | ||
{!example/system/example_process_3.f90!} | ||
``` | ||
|
||
## `wait` - Wait until a running process is completed | ||
|
||
### Status | ||
|
||
Experimental | ||
|
||
### Description | ||
|
||
The `wait` interface provides a method to block the calling program until the specified process completes. | ||
If the process is running asynchronously, this subroutine will pause the workflow until the given process finishes. | ||
Additionally, an optional maximum wait time can be provided. If the process does not finish within the specified time, | ||
the subroutine will return without waiting further. | ||
|
||
On return from this routine, the process state is accordingly updated. | ||
This is useful when you want to wait for a background task to complete, but want to avoid indefinite blocking | ||
in case of process hang or delay. | ||
|
||
|
||
### Syntax | ||
|
||
`call ` [[stdlib_subprocess(module):wait(subroutine)]] `(process [, max_wait_time])` | ||
|
||
### Arguments | ||
|
||
`process`: Shall be a `type(process_type)` object representing the external process to monitor. | ||
This is an `intent(inout)` argument, and its state is updated upon completion. | ||
|
||
`max_wait_time` (optional): Shall be a `real` value specifying the maximum wait time in seconds. | ||
If not provided, the subroutine will wait indefinitely until the process completes. | ||
|
||
### Example | ||
|
||
```fortran | ||
{!example/system/example_process_2.f90!} | ||
``` | ||
|
||
## `update` - Update the internal state of a process | ||
|
||
### Status | ||
|
||
Experimental | ||
|
||
### Description | ||
|
||
The `update` interface allows the internal state of a process object to be updated by querying the system. | ||
After the process completes, the standard output and standard error are retrieved, if they were requested, and loaded into the `process%stdout` and `process%stderr` string variables, respectively. | ||
|
||
This is especially useful for monitoring asynchronous processes and retrieving their output after they have finished. | ||
|
||
### Syntax | ||
|
||
`call ` [[stdlib_subprocess(module):update(subroutine)]] `(process)` | ||
|
||
### Arguments | ||
|
||
`process`: Shall be a `type(process_type)` object representing the external process whose state needs to be updated. | ||
This is an `intent(inout)` argument, and its internal state is updated on completion. | ||
|
||
### Example | ||
|
||
```fortran | ||
{!example/system/example_process_5.f90!} | ||
``` | ||
|
||
## `kill` - Terminate a running process | ||
|
||
### Status | ||
|
||
Experimental | ||
|
||
### Description | ||
|
||
The `kill` interface is used to terminate a running external process. It attempts to stop the process and returns a boolean flag indicating whether the operation was successful. | ||
This interface is useful when a process needs to be forcefully stopped, for example, if it becomes unresponsive or if its execution is no longer required. | ||
|
||
### Syntax | ||
|
||
`call ` [[stdlib_subprocess(module):kill(subroutine)]] `(process, success)` | ||
|
||
### Arguments | ||
|
||
`process`: Shall be a `type(process_type)` object representing the external process to be terminated. | ||
This is an `intent(inout)` argument, and on return is updated with the terminated process state. | ||
|
||
`success`: Shall be a `logical` variable. It is set to `.true.` if the process was successfully killed, or `.false.` otherwise. | ||
|
||
### Example | ||
|
||
```fortran | ||
{!example/system/example_process_4.f90!} | ||
``` | ||
|
||
## `sleep` - Pause execution for a specified time in milliseconds | ||
|
||
### Status | ||
|
||
Experimental | ||
|
||
### Description | ||
|
||
The `sleep` interface pauses the execution of a program for a specified duration, given in milliseconds. | ||
This routine acts as a cross-platform wrapper, abstracting the underlying platform-specific sleep implementations. | ||
It ensures that the requested sleep duration is honored on both Windows and Unix-like systems. | ||
|
||
### Syntax | ||
|
||
`call ` [[stdlib_system(module):sleep(subroutine)]] `(millisec)` | ||
|
||
### Arguments | ||
|
||
`millisec`: Shall be an `integer` representing the number of milliseconds to sleep. This is an `intent(in)` argument. | ||
|
||
### Example | ||
|
||
```fortran | ||
{!example/system/example_sleep.f90!} | ||
``` | ||
|
||
## `is_windows` - Check if the system is running on Windows | ||
|
||
### Status | ||
|
||
Experimental | ||
|
||
### Description | ||
|
||
The `is_windows` interface provides a quick, compile-time check to determine if the current system is Windows. | ||
It leverages a C function that checks for the presence of the `_WIN32` macro, which is defined in C compilers when targeting Windows. | ||
This function is highly efficient and works during the compilation phase, avoiding the need for runtime checks. | ||
|
||
### Syntax | ||
|
||
`result = ` [[stdlib_system(module):is_windows(function)]] `()` | ||
|
||
### Return Value | ||
|
||
Returns a `logical` flag: `.true.` if the system is Windows, or `.false.` otherwise. | ||
|
||
### Example | ||
|
||
```fortran | ||
{!example/system/example_process_1.f90!} | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
ADD_EXAMPLE(process_1) | ||
ADD_EXAMPLE(process_2) | ||
ADD_EXAMPLE(process_3) | ||
ADD_EXAMPLE(process_4) | ||
ADD_EXAMPLE(process_5) | ||
ADD_EXAMPLE(process_6) | ||
ADD_EXAMPLE(process_7) | ||
ADD_EXAMPLE(sleep) |
Oops, something went wrong.