Différences

Ci-dessous, les différences entre deux révisions de la page.

--- tech:bash_bonnes_pratiques [2025/05/19 17:26] – Jean-Baptiste
+++ tech:bash_bonnes_pratiques [2025/05/27 09:39] (Version actuelle) – Jean-Baptiste
@@ Ligne 15: / Ligne 15: @@
 * https://gist.github.com/the-glima/39905476c82a8acf9c81b7cfe08e5f03
 * https://github.com/chenkaie/junkcode/blob/master/bash/Defensive-BASH-Programming.sh
+* https://bertvv.github.io/cheat-sheets/Bash.html
+* https://medium.com/better-programming/defensive-programming-to-create-a-robust-ish-shell-script-d9f21292d08a
+* https://frippertronics.com/posts/defensive_bash_programming.html
+* https://blog.seboss666.info/2020/04/programmation-defensive-en-bash/
+* https://devhints.io/bash
+* https://kvz.io/blog/bash-best-practices.html & https://github.com/kvz/bash3boilerplate/
+* http://unix.stackexchange.com/questions/8759/best-practice-to-use-in-bash
@@ Ligne 68: / Ligne 74: @@
 Voir
-http://kvz.io/blog/2013/11/21/bash-best-practices/
-http://unix.stackexchange.com/questions/8759/best-practice-to-use-in-bash
-== Les "pipes"
+== Les tubes nommés (pipes)
 Source : https://blog.g3rt.nl/retain-exit-status-code-through-pipe.html