A detailed breakdown of named pipes in Murex
Wikipedia describes a named pipe as the following:
In computing, a named pipe (also known as a FIFO for its behavior) is an extension to the traditional pipe concept on Unix and Unix-like systems, and is one of the methods of inter-process communication (IPC). The concept is also found in OS/2 and Microsoft Windows, although the semantics differ substantially. A traditional pipe is “unnamed” and lasts only as long as the process. A named pipe, however, can last as long as the system is up, beyond the life of the process. It can be deleted if no longer used. Usually a named pipe appears as a file, and generally processes attach to it for IPC.
Where Murex differs from standard Linux/UNIX is that named pipes are not special files but rather an object or construct within the shell runtime. This allows for more user friendly tooling and syntactic sugar to implemented around it while largely still having the same functionality as a more traditional file based named pipe.
In Murex, named pipes are described in code as a value inside angle brackets. There are four named pipes pre-configured: <in> (STDIN), <out> (STDOUT), <err> (STDERR), and <null> (/dev/null equivalent).
You can call a named pipe as either a method, function, or parameter.
As a method:
<in> -> command parameter1 parameter2 parameter3**As a function:
command parameter1 parameter2 parameter3 -> <out>**As a parameter:
command <out> <!err> parameter1 parameter2 parameter3<> / read-named-pipe: Reads from a Murex named pipe<stdin>: Read the STDIN belonging to the parent code blocktest: Murex’s test framework - define tests, run tests and debug shell scriptsThis site's content is rebuilt automatically from murex's source code after each merge to the master branch. Downloadable murex binaries are also built with the website.
Last built on Fri May 19 22:45:48 UTC 2023 against commit 54b5f6754b5f67b250bbf7353e83c42ed187802584c3ae3.
Current version is 4.1.6140 which has been verified against 14045 tests cases.