Change Details

Would like to see 'match whole word' switch added for the //find// command. So for example //"That guy's an a-hole!" find ["hole", true]// would return -1 whereas with the current implementation of //find //returns 16. A new command //findLast //with above optional 'match whole word' switch. //"This is a problem, a big-ass problem!" findLast ["a", true]// would return 19 (or whatever) //"This is a problem, a big-ass problem!" findLast "a"// would return 25 (or whatever) A replace command for strings, would use syntax similar to the //select //alternative syntax; [string, index, how many indexes to replace]: //"Hello World" replace ["Kitty", 6, 5]// would return "Hello Kitty"

Would like to see 'match whole word' switch added for the //find// command. So for example //"That guy's an a-hole!" find ["hole", true]// would return -1 whereas with the current implementation of //find //returns 16. A new command //findLast //with above optional 'match whole word' switch. //"This is a problem, a big-ass problem!" findLast ["a", true]// would return 19 (or whatever) //"This is a problem, a big-ass problem!" findLast "a"// would return 25 (or whatever)

Would like to see 'match whole word' switch added for the //find// command. So for example //"That guy's an a-hole!" find ["hole", true]// would return -1 whereas with the current implementation of //find //returns 16. A new command //findLast //with above optional 'match whole word' switch. //"This is a problem, a big-ass problem!" findLast ["a", true]// would return 19 (or whatever) //"This is a problem, a big-ass problem!" findLast "a"// would return 25 (or whatever) A replace command for strings, would use syntax similar to the //select //alternative syntax; [string, index, how many indexes to replace]: //"Hello World" replace ["Kitty", 6, 5]// would return "Hello Kitty"