Oh yeah.
Brain relapse.

Edited.

No.
It would be a value and Axe would search the AppVar for that value.

:"MYVAR->Str1
:"Saved.->Str2
:Select(Str1)
:GetCalc(50)->A
:45->{A+24}
:If inString(Str1,45)
:Disp Str2,i
:End

Something like that.

In this example, we put in two things. We told Axe to look in MYVAR (Str1) for the value 45.
It returned a 1 and as a result, it threw back a "Saved." message.

EDITED.

That's why should always have a copy of the doc at hand when programming. I too find it difficult to remember all of the commands and their syntax. But the more you program, the more chances you have of remembering them.

I was planning to add an instr() command, but a little more general than what you are referring to.  It would be like this:

instr(START,BYTE<,SIZE>)

The last option is optional.  You give it a pointer, and it searches for the byte until it finds it and then returns the pointer to that byte, or it returns zero if not found.  That way, its not just limited to application variables, you can use it anywhere.

Its pretty easy to add, but I haven't yet because honestly, it really isn't as useful as it sounds.  There is a regular assembly instruction that does exactly this called "cpir" but I've never used it or needed to use it ever for anything.  I've almost never seen it used in other programs either.  It would only be needed for very specific applications, and even then its easy to write a subroutine yourself with existing commands.  But yes, I will support it eventually, but its in the back of my list.

In such command, though, how would you specify (in this syntax) if you want to point to a byte in an appvar instead of inside the program?

Select(Str1)
getCalc()->A
instr(A,'Z',100)

This would search for the character 'Z' in the first 100 bytes of the appvar.

Yes, but just like the calc's instr(), it doesn't just return 1, it returns the location of the found byte if it is found (a pointer) because this is much more useful.