Comparing variables

[Gianni]

$1 = "Q"
$2 = "W"
$3 = "Y"
$4 = "U"
$5 = "S"
$6 = "Y"

$c = "Y"

$i=0
$string=$1&$2&$3&$4&$5&$6

Do
    $i+=1
    $ret=StringInStr($string,$c,1,$i)
    MsgBox(0,"",StringReplace($ret,"0","that's all"))
Until $ret=0

MsgBox(0,"",StringTrimRight("no (more)",6*($i=0))&" '"&$c&"' found.")

 

 too many conclusive msgbox ...   one would be sufficient......

Edited August 9, 2013 by Pincopanco

[Edano]

ah you make the rules .....

.

$1 = "Q"
$2 = "W"
$3 = "Y"
$4 = "U"
$5 = "S"
$6 = "Y"

$c = "Y"

$i=0
$string=$1&$2&$3&$4&$5&$6

Do
    $i+=1
    $ret=StringInStr($string,$c,1,$i)
    MsgBox(0,"",StringReplace($ret,"0","that's all"))
Until $ret=0

;MsgBox(0,"",StringTrimRight("no (more)",7*($i=0))&" '"&$c&"' found.")

[BrewManNH]

Wouldn't it just be easier to use the If/Endif statements instead of trying to find some stupid ways around it?

I mean stupid in the sense of this whole exercise, not the examples themselves, some of which are quite interesting.

Just do it the right way, the easiest way, and don't be anal about a few If statements in your code.

[Edano]

$1 = "Q"
$2 = "W"
$3 = "Y"
$4 = "U"
$5 = "S"
$6 = "Y"

$c = "Y"

$i=0
$string=$1&$2&$3&$4&$5&$6
$ret=""

Do
    $i+=1
    $ret&=StringInStr($string,$c,1,$i)&","
Until StringRight($ret,2)="0,"

MsgBox(0,"",$c&StringTrimLeft(" not found in places ",4*($ret<>"0,"))&StringTrimRight($ret,3))

.

anal ?

Edited August 9, 2013 by Edano

[Edano]

in fact, i am a big really big fan of avoiding if's in a script. you can spare a lot of lines by doing it.

[Gianni]

Edano, you're smart,
however, not to be anal , but I was just curious as to a solution found by AutID On His code on post  >#9,

....but never mind.

[AutID]

wow, is this still hot or a competition ???

.

$1 = "Q"
$2 = "W"
$3 = "Y"
$4 = "U"
$5 = "S"

$c = "Y"

$string=$1&$2&$3&$4&$5

MsgBox(0,"",StringInStr($string,$c))

.

E.

Edit: of course, using includes is cheating. you could include every au3 script you want, even self written. this is cheating

I will not even comment this.

 

Wouldn't it just be easier to use the If/Endif statements instead of trying to find some stupid ways around it?

I mean stupid in the sense of this whole exercise, not the examples themselves, some of which are quite interesting.

Just do it the right way, the easiest way, and don't be anal about a few If statements in your code.

I prefer clean projects every time I do one. If statement is the easy way but if I use the easy way everywhere my project will get 3 times bigger without reason.

This is what I am using atm.

Func _Indexreturn()
 Local $values[10] = [$1, $2, $3, $4, $5, $6, $7, $8, $9, $10]
 Local $index = _ArraySearch($values, $aKeys[$c])
 Return $index
EndFunc

I find it better than an If statement but anyway.

 

[BrewManNH]

If you use the obfuscater and just use the /so option to strip unused functions, then open the obfuscated script, you'll see that there's a lot more in your script than you think there is, and a simple if/then/endif would probably make your script much smaller in the long run rather than using the Array UDF and _ArraySearch.

[AutID]

If you use the obfuscater and just use the /so option to strip unused functions, then open the obfuscated script, you'll see that there's a lot more in your script than you think there is, and a simple if/then/endif would probably make your script

I already thought about it but array udf is already included in my script so i don't have a lot to loose. Not all array functions can be replaced with if statements.

Anyway thank you, you seem to be clever

Edited August 10, 2013 by AutID

[Edano]

another passion of mine :.... avoid includes ...... really

I already thought about it but array udf is already included in my script so i don't have a lot to loose. Not all array functions can be replaced with if statements.
Anyway thank you, you seem to be clever

[AutID]

The only way to do what you are saying is to copy the array functions on my own udfs included in my script but come to think of it. A lot of the array functions call each other so in the end i will have to include the udfs. And please stop telling things like these because there are people who will be looking for similar things and read what you are saying

[Edano]

maybe it is YOUR way to copy and paste functions, which is really stupid and senseless. but i use them to learn the logic and apply the learned to my code.

and PLEASE never ever tell me again what i have to say and what not.

[jchd]

Please calm down Edano. AutId wasn't teaching you but was rightfully thinking that such advice you gave wasn't for beginners and needed context to not be taken at face value.

[Edano]

you are right, not for beginners. and i am calm. i said what had to be said. now it's okay.

[guinness]

Even so, advanced AutoIt programmers use Includes, I mean why have a dog and bark yourself!

[Bowmore]

I was amusing myself with creating a few ways of achieving the original challenge that AutID and finding that an If Then structure (no need for any elseif) was the fastest method set, but then I found that the rules had changed.

As a bit of an aside I am puzzled by the number of Autoit users who seem to go to great effort using all sorts of convoluted methods to make their code span as few lines as possible, usually with the result of a slower script in which the logic is harder to follow and debug. Many of the applications that I write often involve manipulating data in huge text files. Many is the number of times that I have managed to make it run ten time faster by adding a few hundred extra lines of code. This is especially true if you have some knowledge of the frequency with which data will occur and branch your code so that the most likely cases are checked first. It's not the total number of lines in your source code that affects the speed of your application, but the number of instructions that need to be executed to complete the task. The rule is where there are many possible routes eliminated the least likely as quickly as possible.