Quote: They are consistent. The first argument or set of arguments is always the regular expression(s), then the string to be search, and lastly the replacement string (if there is one).
Maybe we are looking at different things. Here are the three most recent Regex commands that I saw:
1. @RegexFindString(regular_expression as string, str as string)
2. @RegexBetweenString(reg1 as string, reg2 as string, str as string)
3. @RegexReplaceString(expression as string, str as string, replacement as string)[
I read those as:
1. exp1 / sourcestring
2. exp1 / exp2 / sourcestring
3. exp1 / sourcestring / exp2
This appears to be inconsistent to me. Maybe it's just the newness of the commands here.
Normal @Replace uses sourcestring / exp1 / exp2, It would be good to have same format, with sourcestring first. Most other functions also have sourcestring as first parameter, like @Replace, @ReplaceFir, @ReplaceLas, @Left/Right/MidStr, @Delete, etc.
Again, just a suggestion, figured still time to change it now. What is more important than the syntax consistency though is the actucal functions. Thanks again.