I spent the day writing two new commands:

@RegexFindString(regular_expression as string, str as string) as string - this one finds the every instance of the "regular_expression" in "str" and returns the starting points and lengths as a elements in a string array.

So:

str2 = @RegexFindString("mark", "he is mark, and mark is his name")
 

produces "7;4;17;4" - because "mark" starts at the seventh character and is 4 chars long, and the other "mark starts at the seventeenth character and is also 4 chars long.

The other command is @RegexBetweenString(reg1 as string, reg2 as string, str as string) as string, that returns the string between two regular expressions (reg1 and reg2) in the string "str".

aa = @RegexBetweenString("\<TD\>", "\<\/TD\>", "<TD>Producer: Steven Speilberg</TD>")
 

will return: "Producer: Steven Speilberg"

I used an HTML example, because I envision that the second of these commands, in particular, might be used with HTTPGetHTML and HTTPPostHTML to build applications that can gather information from web sites. For example, you could build an app where the user enters a movie title. The application can then use HTTPGetHTML to query www.imdb.com (the Internet Movie Database) and then uses @RegexBetweenStrings to parse out all of the credits, movie posters, and whatnot for your application.

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). There is never a result passed as an argument, only returned.

Quote:


3. The third argument to @RegexReplaceString is not a regular expression, just an ordinary string.

You really are too good Mark. 

The more you give, the more we will ask for.

Thanks again