#include

[Guest adreher]

Hello,

I am using the #include and #include-once command in my scripts. If I change the functions.au3 - script then I have to recompile all other scripts that include this script otherwise the changes won´t work.

Is this a bug?

functions.au3:

----------------

#include-once

..

..

..

script1.au3:

--------------

#include "c:\scripts\functions.au3"

..

..

..

Thanx

Andi

[jpm]

I was thinking that #include <...> will always refer to the current install include file whatever the script is compile or not.

I don't think I am right, so you really need to recompile all refering scripts

[Jon]

Compiled scripts contain all the includes required to run. It wouldn't be very "standalone" if you still needed to give access to the include files!

[pekster]

adreher, the best way to think about the #include directive is that it will place whatever code is in the include file at that point in your source. Just like any source, if you compile it, it will remain the same even if you change the source code. However, if you change the source of the include file and re-execute your script, it will use the updated include file since it's "pasting" the code from the now changed file.

[Nutster]

The sequence of events:

• Functions.au3 is written
• Script1.au3 is written, #include'ing, Functions.au3
• Script2.au3 is written, #include'ing, Functions.au3
• Script1.au3 is compiled to Script1.exe, with a copy of Functions.au3 included.
• Script2.au3 is compiled to Script2.exe, with a copy of Functions.au3 included.
• Functions.au3 is modified.
• Script1.au3 is re-compiled. The new version of Functions.au3 is included.
• Script2.au3 is left alone. It still contains the old version of Functions.au3

My general recommendation is if Script2.au3 is working without the new Functions.au3, then just leave it. If it is improved by the updated Functions.au3, then recompile it.