You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
46 lines
1.2 KiB
HTML
46 lines
1.2 KiB
HTML
<!DOCTYPE HTML>
|
|
<html>
|
|
<head>
|
|
<title>Closures and Currying in BASH?</title>
|
|
<link rel="stylesheet" type="text/css" href="../../style.css">
|
|
<meta charset="UTF-8">
|
|
</head>
|
|
|
|
<body>
|
|
<a href="../../blog.html">Home</a>
|
|
<article>
|
|
<h1>Closures and Function Currying... in BASH?</h1>
|
|
<p>
|
|
I don't think anyone will disagree with me when I say that GNU BASH is not
|
|
a functional programming language. Some people would probably even argue
|
|
that bash is not a programming language at all. Whatever opinion you may
|
|
have, there is no denying that bash is a damn handy too to have in your
|
|
belt. Today I figured I'd share some functional concepts that have been
|
|
helpful to me when writing scripts in BASH, which is my favorite scripting
|
|
language for workflow automation.
|
|
</p>
|
|
|
|
<h2>Using functions for clarity</h2>
|
|
<p>
|
|
[[ LINK TO YOUTUBE VIDEO FUNCTIONAL TAO OF BASH ]]
|
|
</p>
|
|
|
|
<h2>Using pipes as map/reduce</h2>
|
|
<p>
|
|
</p>
|
|
|
|
<h2>Using recursion to grow state</h2>
|
|
<p>
|
|
</p>
|
|
|
|
<h2>Bonus: A demonstration of a madman, closures and currying in bash</h2>
|
|
<p>
|
|
</p>
|
|
</article>
|
|
</body>
|
|
</html>
|
|
|
|
<!-- Local Variables: -->
|
|
<!-- sgml-basic-offset: 1 -->
|
|
<!-- End: -->
|