Date: Sat, 21 Mar 2009 15:19:05 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Chuck Robey <chuckr@telenix.org> Cc: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>, freebsd-questions@freebsd.org Subject: Re: bash suddenly doesn't like $() syntax Message-ID: <44k56iptue.fsf@lowell-desk.lan> In-Reply-To: <49C532E6.3080903@telenix.org> (Chuck Robey's message of "Sat\, 21 Mar 2009 14\:33\:10 -0400") References: <20090321124859.GA27682@anton.digitaltorque.ca> <20090321142122.GA99623@torus.slightlystrange.org> <44tz5m7sau.fsf@lowell-desk.lan> <49C532E6.3080903@telenix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Chuck Robey <chuckr@telenix.org> writes: > I've had stuff like this happen to me, once in a while. it's NEVER a fact of > bash really suddenly losing something so major. What you have to is to look at > previous parts of your code, for things like unclosed parens, unclosed quotes, > things like that. The errors aren't overly helpful, but if you look at previous > lines, you'll find it there, believe me. That happens, but was not the case in this instance. A particular syntax really did break in bash if you compiled it with our system yacc(1). I don't know whether the problem was in yacc or in the bash build assuming Gnuisms from bison, but bash really was broken for a while on $(...) formulations. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44k56iptue.fsf>