<p dir="ltr">Parsing text in bash is much harder than in Perl. Associative arrays in bash really help.</p>
<div class="gmail_extra"><br><div class="gmail_quote">On Oct 21, 2016 6:33 PM, "Chris Fowler" <<a href="mailto:cfowler@outpostsentinel.com">cfowler@outpostsentinel.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:arial,helvetica,sans-serif;font-size:12pt;color:#000000"><div>Not a rant or question, just a thought.</div><div><br></div><div>I've been working on "Jenga Linux" and since I do not have many perl modules until later in the build of LFS 7.10 I'm sticking to bash as much as possible. GNU STOW is an exception, but it uses perl in /tools from chapter 5 until it can be installed in chapter 6. Beyond that , the only perl module in chapter 5 is XML::Parser. I could install all modules needed in /tools and use them in chapter 6, but I'm forcing myself to expand my bash experience by using what most other disti creators use. </div><div><br></div><div>It would nice to find a book titled: "Bash for Perl Programmers". Very simple tasks I do in Perl are a struggle in bash. Stack Exchange is not short on answers. </div><div><br></div><div>Chris</div></div></div><br>______________________________<wbr>_________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/<wbr>listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/<wbr>listinfo</a><br>
<br></blockquote></div></div>