|
From: | L A Walsh |
Subject: | Re: break no longer breaks out of loops defined in an outer context |
Date: | Wed, 01 Mar 2017 08:48:20 -0800 |
User-agent: | Thunderbird |
Chet Ramey wrote:
On 3/1/17 7:43 AM, Stephane Chazelas wrote:It's not clear what combining several compat options could do. For instance with shopt -s compat31 compat43 would not be compatible with bash-4.3 in that the [[ =~ ]] operator would work the bash-3.1 way. That could cause confusion.Compatibiity options are all mutually exclusive, last one wins.
--- That's not good and relates to my my long-held thought that such compat options should be named for the feature they change and not a specific version (didn't mention it, since I don't use any compat options and have had other issues more important for me). But the way it is now -- if someone is using a compat option for an earlier version, and now needs another compat option for some other incompat, then they have a problem. I'm fairly sure that wasn't by design, as the compat options seem to have been meant to solve specific compat problems that people needed, as they came up -- not as a new, long-term feature to control various compat issues. -l
[Prev in Thread] | Current Thread | [Next in Thread] |