Actually, that example doesn't work.* (You idiot! Who posted that?) This ugly work-around is more functional in bash:
shopt -s lastpipe; set +m; echo hello|read foo; set -m; echo $foo
* The eval is evaluated in the subshell, and my $foo$bar was set from previous experiments.
Still doesn't seem to set "$foo" in the current shell as with ksh.
Certainly true. If you like hoop jumping, you can do it.
echo "there hello" | eval `(read t h; echo foo=$h bar=$t)`; echo $foo $bar
hello there
**ducks for cover**
% echo hello | (read foo; echo "foo: $foo ($SHELL)")
foo: hello (/bin/bash)
[Angry customer]: The software I was using crashed with an assert code!
[St. Peter]: Yes, we'll have to talk to the car manufacturer about that.
Most of the software I work on can emit smoke, mangle parts, or lose data if it were to abort. There's a place for assert(), but it's not always an option.
It's equally valid to say that cash has increased in value by 400% against cryptocurrency. You should buy dollars now! Disclaimer: some cryptocurrency people are saying that the current value of cash is just a bubble.
In other news, cash held fairly steady against other easily tradable commodities, with no major movement.
Cars last about 15 years. They can last 50, or 5. When you replace them depends on the economics of keeping them running. When you can't get service techs, and parts shoot up in price, you figure out how to migrate to and finance a less expensive car.
If your local police department was running a fleet of 30 year old Ford LTD Crown Vics you would rightfully question the economics. And (possibly) rightfully decide to keep them running.
Lotus Notes is nearly 30 years old, though its architecture dates to the early 70s.
Mirrors should reflect a little before throwing back images. -- Jean Cocteau