Unknown function name - unexpected error

[BrewManNH]

 

Remarks:

in all script I use #include-once at the very top of the script

I would like to suggest not doing this, you only need this line in files that are to be included into another script. It is never needed in the main script itself

[mLipok]

I would like to suggest not doing this, you only need this line in files that are to be included into another script. It is never needed in the main script itself

Yes, you have right.

I formulated my statement incorrectly.

[mLipok]

Interesting - If you have the second #include-once before the line #include "15.au3" the script works without problem - it is only if the second #include-once is placed after that point that the error occurs.

 

Indeed, interesting.

If you like such trivia, it also see here.

[Melba23]

mLipok,

I had already noticed that - but I imagined that the whole file was being so corrupted by the #include-once problem that Au3Stripper was giving up as well.

I have amended the Remarks for #include-once:

It is quite common to have the same "#include <filename.au3>" line in several of the files included included in a script. If the same file were to be included several times, it is quite likely that this would generate a "Duplicate function" or "Cannot redeclare a Const" error. So when writing a script intended for use as an include file, add #include-once to prevent that file from being included more than once.  Note that the #include-once line must be placed at the top of the script and before any other #include lines.

It is not recommended to add a #include-once line to scripts which are not intended to be used as include files within other scripts.

M23

[mLipok]

I have amended the Remarks for #include-once:

It is quite common to have the same "#include <filename.au3>" line in several of the files included included in a script. If the same file were to be included several times, it is quite likely that this would generate a "Duplicate function" or "Cannot redeclare a Const" error. So when writing a script intended for use as an include file, add #include-once to prevent that file from being included more than once.  Note that the #include-once line must be placed at the top of the script and before any other #include lines.

It is not recommended to add a #include-once line to scripts which are not intended to be used as include files within other scripts.

 

Great.

[mLipok]

AutoIt first loads ALL external files, merges them with the main script and then executes this expanded script.

 

And now I have different experience , but maybe I'am  wrong.

 

 

 

here is my repro for Water statement

---

 

First use this script to create testing UDF :

FileDelete("1.au3")
FileWriteLine("1.au3", "Global $__var1 = 1")
FileDelete("2.au3")
FileWriteLine("2.au3", "Global $__var2 = 2")
FileDelete("3.au3")
FileWriteLine("3.au3", "Global $__var3 = 3")

 

 

now you can chceck one of this scirpt:

REPRO SCRIPT 1:

#AutoIt3Wrapper_Run_Au3Check=N
#include "1.au3"
ConsoleWrite("$__var1 = " & $__var1 & @CR)

ConsoleWrite("$__var2 = " & $__var2 & @CR) ; here is error message "Variable used without being declared."
#include "2.au3"

#include "3.au3"
ConsoleWrite("$__var3 = " & $__var3 & @CR)

REPRO SCRIPT 2:

#include "1.au3"
ConsoleWrite("$__var1 = " & $__var1 & @CR)

If False Then
    #include "2.au3"
EndIf
ConsoleWrite("$__var2 = " & $__var2 & @CR) ; here is error message "Variable used without being declared."

If True Then
    #include "3.au3"
    ConsoleWrite("$__var3 = " & $__var3 & @CR)
EndIf

[BrewManNH]

You include 2.au3 AFTER the line referencing the variable that is declared inside it.

 

This file will look like this when it runs.

#AutoIt3Wrapper_Run_Au3Check=N
Global $__var1 = 1
ConsoleWrite("$__var1 = " & $__var1 & @CR)

ConsoleWrite("$__var2 = " & $__var2 & @CR) ; here is error message "Variable used without being declared."
Global $__var2 = 2
Global $__var3 = 3
ConsoleWrite("$__var3 = " & $__var3 & @CR)

#include files are added to the script at the point you place the #include directive. That's why it is recommended to put all #include lines at the top of the script, otherwise you have issues like this where the user is unaware of how #include works. Edited July 24, 2014 by BrewManNH

[mLipok]

here is my repro for Water statement

I think say it was clear.

 

 

You include 2.au3 AFTER the line referencing the variable that is declared inside it.

 ....

#include files are added to the script at the point you place the #include directive. That's why it is recommended to put all #include lines at the top of the script, otherwise you have issues like this where the user is unaware of how #include works.

 

I know that.

 

But I want to do example that show , the AutoIt behavior is far from @water speeches

 

AutoIt first loads ALL external files, merges them with the main script and then executes this expanded script.

 

Well, unless I'm wrong or hastily understand @water speeches ?

 

---

What you think about REPRO SCRIPT 2.

Does this mean that the execution of the # include directive, generally speaking, can conditioned ?

btw.

I found similar topic.