DefinePostfixOprt， defining both "m" and "mm" as postfix operators can lead to conflicts

[xiayezhiying]

m_parser->DefinePostfixOprt（mmOprt）; // "mm"
m_parser->DefinePostfixOprt（mOprt）; // "m"
m_parser->SetExpr("1mm");
m_parser->Eval().GetFloat(); // error

[beltoforion]

Just for curiosity, What happens if you define the longer one last? I suspect it will work then.

[xiayezhiying]

Just for curiosity, What happens if you define the longer one last? I suspect it will work then.

Eval()->ParseFromString()->ReadNextToken()
then throw a Error.
err.Errc=ecUNASSIGNABLE_TOKEN;
err.Expr="1mm";
err.Pos=2;
err.Ident= "m"

[xiayezhiying]

Just for curiosity, What happens if you define the longer one last? I suspect it will work then.

bool TokenReader::IsPostOpTok(ptr_tok_type &a_Tok)
{
for (item = m_pPostOprtDef->begin(); item != m_pPostOprtDef->end(); ++item)
{
if (sTok.find(item->first) != 0)
continue; //“mm".find("m") == 0
}
}

Can find here be replaced with ==

[xiayezhiying]

Just for curiosity, What happens if you define the longer one last? I suspect it will work then.

define "mm" last , or define "m" last. it still doesn't work properly.
mutable oprt_pfx_maptype *m_pPostOprtDef;
m_pPostOprtDef is a map.