fixed a bug: the parser now correctly parses parameters of the form
-Pvalue This will now produce 'value'. The buggy parser would parse 'alue' here. I am truly and deeply ashamed to have created such an off-by-one error. Marc assumed this was wanted behaviour (so that it should read: -P=value) I must admit that this is a logical conclusion, though it was merely a side-effect of the error. To not force Marc to rewrite the tutorial and his way of working with EO, I decided to make a feature out of the bug, so that now the parser will parse: -Pvalue -P=value and of course the true and blue: -Parameter=value I will now go and check if I sent out some crappy papers caused by this bug (as I've been using eo!)
This commit is contained in:
parent
680229507f
commit
262869d0ae
1 changed files with 19 additions and 7 deletions
|
|
@ -179,9 +179,21 @@ void eoParser::readFrom(istream& is)
|
||||||
}
|
}
|
||||||
else // it should be a char
|
else // it should be a char
|
||||||
{
|
{
|
||||||
string value = "1";
|
string value = "1"; // flags do not need a special
|
||||||
if (str.size() > 2)
|
|
||||||
|
if (str.size() >= 2)
|
||||||
|
{
|
||||||
|
if (str[2] == '=')
|
||||||
|
{
|
||||||
|
if (str.size() >= 3)
|
||||||
value = string(str.begin() + 3, str.end());
|
value = string(str.begin() + 3, str.end());
|
||||||
|
}
|
||||||
|
else
|
||||||
|
{
|
||||||
|
value = string(str.begin() + 2, str.end());
|
||||||
|
}
|
||||||
|
}
|
||||||
|
|
||||||
shortNameMap[str[1]] = value;
|
shortNameMap[str[1]] = value;
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
|
||||||
Reference in a new issue