StringInStr / StringReplace

[Chris_1013]

Is there any reason why StringInStr and StringReplace have the casesense and occurance options different ways round?

i.e;

StringInStr ( "string", "substring" [, casesense [, occurance]] )

StringReplace ( "string", "searchstring", "replacestring" [, count [, casesense]] )

Only just something I've noticed, don't expect it to change as it's too far down the road now.

[Jon]

occurance was only just added, and you can't change the order as it breaks any old scripts that were using the case sense option.

[CyberSlug]

Ack, my internet connection ate my post

What Jon said. Also, you could argue that the last optional paramter is less likely to be used than the paramter before it.

Some window functions list x,y followed by (optional) width,height while some other window functions list width,height followed by (optional x,y).

[jhbell]

Is there any reason why StringInStr and StringReplace have the casesense and occurance options different ways round?

i.e;

StringInStr ( "string", "substring" [, casesense [, occurance]] )

StringReplace ( "string", "searchstring", "replacestring" [, count [, casesense]] )

Only just something I've noticed, don't expect it to change as it's too far down the road now. 

Please help me out.. my documentation does not include occurance in StringinStr nor does my AutoIt accept 4 args. Please explain.

[pekster]

Please help me out.. my documentation does not include occurance in StringinStr nor does my AutoIt accept 4 args.  Please explain.

What version are you using? You need the latest unstable build to use any functions that have been developed recently (such as additional commands, modifications to existing ones, and the GUI function calls.)