Hi,
I needed to intensively use str_stri for a osm hypertext parser I am writing and I realized that it got slower the bigger the parsed strings or char buffers were. In the try of indetifying the problem I substituted all the str_stri calls by my own function and surprisingly it solved the problem. I could not believe it.

Did you also try in published mode?

I don't know the engine code - but for sure there's a certain chance that in development mode there are debug routines active for detecting array out of bounds and the like.

There is some overhead in development mode, but it should not make much difference. str_stri is in fact very slow, as far as I can see in the source code. Your function is much faster. I don't see at a first glance why str_stri is coded this way, maybe it's due to some special case handling. As long as you don't use unicode or some STRING specific stuff I recommend that you continue with your own function.

Thank you for your answers!
I will go this way. Maybe a chr_cmp is a good choice too.

Salud!