Fix bug where processDefaultValues reads past the first '=' #991
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If traits defaults are specified by the user in the form
value="$(dateTrait.value=68BO_2011.0=2011.0,65BO_2013.0=2013.0,97SGR_2012.0=2012.0..."
BEAST would read past the first '=' to the last '='. This makes the parserDefinitions key equal "dateTrait.value=68BO_2011.0=2011.0,65BO_2013.0=2013.0,97SGR_2012.0" and value "2012.0". I fixed this by only setting k to the index of the first '='.