Possible ObjCreate problem with new AutoIt version

[Katharsis]

...or maybe with the way it now communicates with CDO.DropDirectory.

We have a script that monitors e-mails that come in to a drop directory. The script looks at the e-mails and sends a response accordingly to the user that sent the e-mail. However, after updating to the latest AutoIt, I cannot compile due to a supposed syntax error which does not exist.

Here is the relevant code:

$objDropDirectory = ObjCreate("CDO.DropDirectory")
$colMessageCollection = $objDropDirectory.GetMessages($DropFolder)
If $colMessageCollection.Count > 0 Then
   For $msg In $colMessageCollection
   $fileFullPath = $colMessageCollection.Filename($msg)
      If StringInStr($msg.To, "daily", 2) Then
         ...do stuff...
      EndIf
   Next
EndIf

The error I receive upon compiling is this:

(36,26) : ERROR: missing separator character after keyword.
   If StringInStr($msg.To,

Clearly, there is a separator character. The comma is right there. This wasn't happening before 3.3.8.x. Any ideas?

Edited April 10, 2012 by Katharsis

[ProgAndy]

Is this error from Au3Check or from the compiler? If possible try to ignore it. What happens if you add a space after .To?

Propably Au3Check messes up since To is a keyword when using the for-loop.

Edited April 10, 2012 by ProgAndy

[Jos]

What version of AU3check you are getting this warning from as the current Beta doesn't give this error for me with the posted snippet.

[KaFu]

AU3Check (1.54.22.0) throws the same error message for me too. Maybe just change $msg.To to $msg.To()?

Edited April 10, 2012 by KaFu

[Katharsis]

The parentheses fixed it. Thanks!

Also, the Au3Check is version 1.54.22.0.

[Melba23]

Katharsis,

This was covered in the v3.3.8.0 changelog:

"Changed: Parentheses are required when invoking objects after all method names in order to have correct internal handling"

Always worth a look in there when you upgrade.

M23

[trancexx]

How would AU3Check know if .To is method or property?

This has nothing to do with that. This was a bug in AU3Check where it was confusing AutoIt's keywords and object prop/methods. It was fixed some time ago.

It's wrong to use parentheses here.

Edited April 11, 2012 by trancexx

[lsakizada]

I have instaled today latest autoit (Scite 14.01.22.21, AU3 v3.3.12.0, Beta v3.3.13.19) and encounter the same issue.

I added parentheses to the method name and this not help to rsolve the error:

Here is the error and the function (from SMTP UDF):

>Running AU3Check (3.3.12.0)  from:C:\Program Files (x86)\AutoIt3  input:C:\Automation\tmp\UI7.au3
"C:\Automation\tmp\includes\OnAutoItErrorRegister.au3"(565,15) : error: missing separator character before keyword.
    $objEmail.To
~~~~~~~~~~~~~~^
"C:\Automation\tmp\includes\mailer.au3"(33,15) : error: missing separator character before keyword.
    $objEmail.To
~~~~~~~~~~~~~~^

Func __OnAutoItErrorRegister_INetSmtpMailCom($s_SmtpServer, $s_FromName, $s_FromAddress, $s_ToAddress, $s_Subject = "", $s_Body = "", $s_CcAddress = "", $s_BccAddress = "", $s_Username = "", $s_Password = "", $IPPort = 25, $ssl = 0)
    Local $objEmail = ObjCreate("CDO.Message")
    If Not IsObj($objEmail) Then Return SetError(1, 0, 0)

    $objEmail.From = '"' & $s_FromName & '" <' & $s_FromAddress & '>'
    $objEmail.To = $s_ToAddress

    Local $i_Error = 0
    Local $i_Error_desciption = ""

    If $s_CcAddress <> "" Then $objEmail.Cc = $s_CcAddress
    If $s_BccAddress <> "" Then $objEmail.Bcc = $s_BccAddress

What am I supposed to do to resolve this issue?

Thanks

[water]

Install the latest Beta version of AutoIt.

[lsakizada]

Install the latest Beta version of AutoIt.

 

I did it and mentioned the version in my previous post.

It is 3.3.13.19.

Downloaded from here: https://www.autoitscript.com/autoit3/files/beta/autoit/

 

It is not working.

Thanks

Edited November 4, 2014 by lsakizada

[water]

Sorry, missed that

This >bug has been reported a few times and the latest beta always resolved the issue.

[lsakizada]

Sorry, missed that

This >bug has been reported a few times and the latest beta always resolved the is

 

 

Is there any chance that the bug was inserted in the latest beta again?

As much as I understood this is a bug of AU3Check,

maybe this tool is still buggy?

Regards

[water]

DIdn't have this problem myself. But it seems that the latest beta solved the problem for the other users.

[lsakizada]

Hi Water, thanks for the reply.

Anyway, I reinstall and install the all Autoit components several times with different options for 32/64 bit and made sure the installation folder is clean

but, the error still exists.

I think it is a bug that was not resolved completely.

Edited November 4, 2014 by lsakizada

[water]

When I run the SciTE "SyntaxCheck Prod" tool for your code I get the same error.

When I run the SciTE "SyntaxCheck Beta" tool for your code I get no error. Beta = 3,3.13.19

You are sure you run the Beta version?

Can you post the Scite output?

[BrewManNH]

The problem isn't in AutoIt, it's in Au3Check and has been fixed in the latest version of that tool.

[water]

But Au3Check is part of the AutoIt download as described in post #10, isn't it?

I suspect the OP has installed the latest beta, but doesn't run the SyntaxCheck Beta.

[lsakizada]

When I run the SciTE "SyntaxCheck Prod" tool for your code I get the same error.

When I run the SciTE "SyntaxCheck Beta" tool for your code I get no error. Beta = 3,3.13.19

You are sure you run the Beta version?

Can you post the Scite output?

 

This is the output:

Look like it is indeed running the  AU3Check (3.3.12.0). How come?

BTW: The Compiler is running the same version AU3Check (3.3.12.0).

In the compiler: Running Beta + "Run AU3Check before compilation" checkbox is checked BUT the AU3Check version is still kept AU3Check (3.3.12.0).

EDIT: There is a little bug in the presentation of the AU3Check (3.3.12.0). Its corrected itself after running as beta and restarting the UI.

I think my issue is resolved.

>"C:\Program Files (x86)\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.exe" /run /prod /ErrorStdOut /in "C:\Automation\tmp\UI7.au3" /UserParams    
+>08:30:43 Starting AutoIt3Wrapper v.14.801.2025.0 SciTE v.3.4.4.0   Keyboard:00000409  OS:WIN_7/Service Pack 1  CPU:X64 OS:X64    Environment(Language:0409)
+>         SciTEDir => C:\Program Files (x86)\AutoIt3\SciTE   UserDir => C:\Users\bik\AppData\Local\AutoIt v3\SciTE\AutoIt3Wrapper   SCITE_USERHOME => C:\Users\bik\AppData\Local\AutoIt v3\SciTE 
>Running AU3Check (3.3.12.0)  from:C:\Program Files (x86)\AutoIt3  input:C:\Automation\tmp\UI7.au3
"C:\Automation\tmp\includes\OnAutoItErrorRegister.au3"(566,12) : error: missing separator character before keyword.
    $objEmail.To
    ~~~~~~~~~~^
"C:\Automation\tmp\includes\mailer.au3"(33,15) : error: missing separator character before keyword.
    $objEmail.To
~~~~~~~~~~~~~~^
C:\Automation\tmp\UI7.au3 - 2 error(s), 0 warning(s)
!>08:30:44 AU3Check ended. Press F4 to jump to next error.rc:2
+>08:30:44 AutoIt3Wrapper Finished.
>Exit code: 2    Time: 1.458

Edited November 9, 2014 by lsakizada

[water]

Great. I knew the problem would be solved by using the correct version of Au3Check.

[Jefrey]

Sorry for posting on a 3 years old post, but 3 years later this bug seems not to have been fixed on the production version...

I can't use properties that have names like keywords (I'm having the exact problem, the property name is also 'To').

Luckly, I'm developing the object, so I'm able to change the "To" property name to something else. Do I still need to use Beta version to have the fix?

Edited July 1, 2015 by Jefrey