Jump to content
Sign in to follow this  
jpm

3.1.1++

Recommended Posts

I don't remember seeing these, but I know that *= += -= and etc are included, but is there any chance that != [and ==] as well? I've been using PHP for the longest time, and it's unnatural for me to use '<>'.

Thanks!


Writing AutoIt scripts since
_DateAdd("d", -2, _NowCalcDate())

Share this post


Link to post
Share on other sites

I don't remember seeing these, but I know that *= += -= and etc are included, but is there any chance that != [and ==] as well?  I've been using PHP for the longest time, and it's unnatural for me to use '<>'.

Thanks!

<{POST_SNAPBACK}>

I'm used to PHP as well, but we couldn't institute the == because AutoIt already uses it (for case sensitive comparison). I still use != sometimes and am confused when the script errors out.

Back to the original topic, just wanted to mention that the Help file doesn't have an index for GUIEventCompatibilityMode or whatever the option's name is.

Share this post


Link to post
Share on other sites

Back to the original topic, just wanted to mention that the Help file doesn't have an index for GUIEventCompatibilityMode or whatever the option's name is.

True I forget to add it in the next upload 3.1.1.11 :)

Thanks :D

Share this post


Link to post
Share on other sites

I'm used to PHP as well, but we couldn't institute the == because AutoIt already uses it (for case sensitive comparison). I still use != sometimes and am confused when the script errors out.

<{POST_SNAPBACK}>

The only way to test case sensitive string inequality is by Not ($a == $:), so for that != would maybe be nice. However, I fear that many would be tempted to use != for normal number inequality comparison, which could fail, so it's best not to add it. (e.g: 2 <> "2.0" vs. 2 != "2.0").

PS. Bug: I just found that the == operator returns Int instead of Bool.

Try: MsgBox(0, (1 = 1), (1 == 1))


blub

Share this post


Link to post
Share on other sites

I can understand '==', but couldn't != apply to strings and number strings as well?


Writing AutoIt scripts since
_DateAdd("d", -2, _NowCalcDate())

Share this post


Link to post
Share on other sites

The only way to test case sensitive string inequality is by Not ($a == $:), so for that != would maybe be nice. However, I fear that many would be tempted to use != for normal number inequality comparison, which could fail, so it's best not to add it.  (e.g: 2 <> "2.0" vs. 2 != "2.0").

PS. Bug: I just found that the == operator returns Int instead of Bool.

Try: MsgBox(0, (1 = 1), (1 == 1))

<{POST_SNAPBACK}>

on PS comment

If it is a bug I think there are other because for now all Is... return Int.

As you are the leader on the Boolean can you clean the situation.

Valik ask for Bool() function perhaps a IsBool is needed to be completly coherent.

Share this post


Link to post
Share on other sites

Could you add the @HotkeyPressed macro, please?

<{POST_SNAPBACK}>

Holger didn't submit any modification for This. I hope it will see your message and send the modifications Edited by jpm

Share this post


Link to post
Share on other sites

I'm looking to do the same with Booleans:

$bool = Bool(IniRead($sIni, $sSection, $sKey, $sDefault))
I am not sure this one will not generate non english user a lot of questions.

in french "True" = "Vrai", "Yes"= "Oui", "1"="1".

The lastest seems usually agreed from any language perhaps not in all user mind(Joke) :)

Share this post


Link to post
Share on other sites

I am not sure this one will not generate non english user a lot of questions.

in french "True" = "Vrai", "Yes"= "Oui", "1"="1".

The lastest seems usually agreed from any language perhaps not in all user mind(Joke) :idiot:

<{POST_SNAPBACK}>

jpm,

On a french Windows: Does a VBscript program like:

Msgbox 1=1

Show "True" or "Vrai" ?

-Sven

Share this post


Link to post
Share on other sites

jpm,

On a french Windows: Does a VBscript program like:

Msgbox 1=1

Show "True" or "Vrai" ?

-Sven

<{POST_SNAPBACK}>

The answer is "Vrai"

Share this post


Link to post
Share on other sites

@jpm: can send you this the next days - when I have anough time to check again with current version...

So long... :D

Holger

<{POST_SNAPBACK}>

fine with the merger :)

Share this post


Link to post
Share on other sites

20th April 2005 - v3.1.1.11 (beta) COM23/24 merge

Fixed : VC7 warnings (Thanks Sven).

Fixed : An Object reference leak in DLLCall().

Added: Support for Arrays returned from COM functions.

Fixed : A FOR..IN loop would still start when an Array contained no elements.

Changed : Return,@error, @extended have to be explicit to be return by an UDF (Thanks Valik)

Check carefully @error and @extended checking and report if pb

Share this post


Link to post
Share on other sites

Have you forgotten to upload the files ?  :)

<{POST_SNAPBACK}>

No but I take a while beind a 56K line so they were OK at 11:11 my time

Usually I wait the end before posting message but as I want to go to bed earlier I did it simultaneously so that the reason you see the post before the files.

Thanks for your testing. :D

Just return on change on return,@error,@extended behavior

Share this post


Link to post
Share on other sites

21th April 2005 - v3.1.1.12 (beta) COM25 merge

Fixed : more than 15 GUI creation (Thanks Wb_Freekill, herewasplato)

Fixed : Reference count problem when passing an Object variable as COM-function argument (thanks dwerznec).

Fixed : Memory leak in COM-Array conversions.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...