so it > would seem we either have to make a mess of the code (switch/case with > 17 FullMatch calls for example) or study the Arg class in order to use > it properly. It's your call.
I don't want to try to understand Arg, so I would vote for the case statement. However, before we do that lets make sure that the AssignToVar code I have works. For the example with "s", "i" that failed, can we do soem debug output t just after the call to fullmatch to check the value of n and s[0] and s[1]? Something like char szbuf[200]; sprintf(szbuf, "%u %s %s", n, s[0].c_str(), s[1].c_str())); g_ppsv-?Debug(szbuf, "","","","",""); > > If you have any doubts about what's not clicking, I suggest you modify > your code to gather the relevant debugging information and dump that > into a PP variable before returning from FullMatch. But any other > practical debugging method is fine with me. If the above shows the s[i] is set, then we need to debug assigntovar. Else lets go with case statement.
