Category:UnixPipes: Difference between revisions

From Rosetta Code
Content added Content deleted
(New page: Unix Pipes with out using any turing complete sublanguages. The attempt is to solve programming problems using the pipelines alone. The tools are not restricted to the commonly available t...)
 
(Fixed up, linkified, language template(?))
Line 1: Line 1:
Unix Pipes with out using any turing complete sublanguages. The attempt is to solve programming problems using the pipelines alone. The tools are not restricted to the commonly available tools in unix. Any new tool is allowed as long as it is sharp enough. (i.e does one and only one thing very well).
{{language}}'''Unix Pipes''' is a collection of tools which doesn't use any Turing complete sublanguages. The idea of the system is to solve programming problems using only the pipelines alone. The tools are not restricted to the commonly available tools in [[UNIX]]. Any new tool is allowed as long as it is sharp enough. (i.e does one and only one thing very well).


It does not include programming problems solved with normal shell by using the control structures available as a part of shell.
It does not include programming problems solved with normal shell by using the control structures available as a part of shell.


A description of the new tool being introduced is required.
If a new tool is introduced, a description of the tool is required.

Revision as of 18:05, 6 April 2008

Language
UnixPipes
This programming language may be used to instruct a computer to perform a task.
See Also:


Listed below are all of the tasks on Rosetta Code which have been solved using UnixPipes.

Unix Pipes is a collection of tools which doesn't use any Turing complete sublanguages. The idea of the system is to solve programming problems using only the pipelines alone. The tools are not restricted to the commonly available tools in UNIX. Any new tool is allowed as long as it is sharp enough. (i.e does one and only one thing very well).

It does not include programming problems solved with normal shell by using the control structures available as a part of shell.

If a new tool is introduced, a description of the tool is required.