Hi Fabio,

>- use of the string variables into VFP command.
>

? LEN(m.String)
? LEN(@m.String)  && don't copy the string into the VM buffer

I've wondered as well why such an approach seems to be missing. Only because of Len(StrTran(,,)) or Len(alltrim()) contructs ? Could the parser use MDotted variables to automatically use such an optimization across other vfp internal functions ? And this seems to have gotten worse in vfp9, probably some checks against buffer overruns.

>and many others are more useful.
A few of my pet peeves: I'ld like to have an option to mark a function called as "inline".
In the case of redundancy saving 1 - 3 liners without need of a local stack this can eliminate the call overhead of a function in often called loops. And NO redundancy in the code <g>!
Or perhaps have a new keyword specifying [optimize..nooptimize] for each condition:
sometimes for an application it makes sense to have multiple indices describing subset filtering, while at certain queries I'ld like to use only a specific index with high selectivity - relieving me from those ugly if seek() - scan while constructs. Probably the best way to speed up apps with large dbf's or LAN-bottlenecks.

regards

thomas