r251524 - [analyzer] Make inclusion/exclusion of checkers less ambiguous.

[Devin Coughlin via cfe-commits]

> On Oct 28, 2015, at 9:28 AM, Anton Yartsev via cfe-commits <cfe-commits at lists.llvm.org> wrote:
> 
> Author: ayartsev
> Date: Wed Oct 28 11:28:57 2015
> New Revision: 251524
> 
> URL: http://llvm.org/viewvc/llvm-project?rev=251524&view=rev
> Log:
> [analyzer] Make inclusion/exclusion of checkers less ambiguous.
...
> 
> my @AnalysesToRun;
> -foreach (@{$Options{EnableCheckers}}) { push @AnalysesToRun, "-analyzer-checker", $_; }
> -foreach (@{$Options{DisableCheckers}}) { push @AnalysesToRun, "-analyzer-disable-checker", $_; }
> +foreach (keys %{$Options{EnableCheckers}}) { push @AnalysesToRun, "-analyzer-checker", $_; }
> +foreach (keys %{$Options{DisableCheckers}}) { push @AnalysesToRun, "-analyzer-disable-checker", $_; }

Does keys guarantee a stable iteration order across different invocations of scan-build? I think it is important that the environment scan-build sets up be deterministic.

Devin