Is it possible to include UDFs in AutoIt's built in function list

[kcvinu]

Hi all,

There is a lot of udfs in autoit. I wonder why don;t they include some most used udfs to autoit's own function list. If they do, then we can avoid a line of code(#include line). Is there any technical reason behind it. ?

[guinness]

If that's your only reason because of one less line, then no, it's pointless. If you would've said "Hey, function x and y perhaps could be included in the core because a] it's a function that has wide usage and b] there might be a possible performance gain in doing so e.g. FileReadToArray()" then maybe your post would have merit. But for typing one less line. There is also a benefit to having UDFs, one of which is transparency of code and for those to learn AutoIt on a practical scale.

[kcvinu]

So i got two reasons for maintaining udfs separate from the core. Is there  any benefit in learning when a function is outside the core ? Correct me if i am wrong.

[jvanegmond]

I think we need a package manager for AutoIt to solve this problem. A lot of languages already adopted this way. A UDF shipped with AutoIt would be no different from any other user defined library and it would be very convenient, possibly even more convenient than how it works now, to include libraries into your project.

[AndyG]

Hi,

After writing my code into Scite, I press the F2-key which runs OrganizeIncludes. All required files are "included" automatically, not only UDF´s.

No typing of #include<blahblah.au3> by hand since years!

OrganizeIncludes runs some seconds, this is the only reason why i combined it not with the F5-Key-LUAMacro...

 Is there  any benefit in learning when a function is outside the core ? 

Yes, of course! And an other great advantage is that you are able to modify existing UDF-code to your own requirements!

Edited August 13, 2015 by AndyG

[kcvinu]

Yes, i agree with manadar. A package manager will do the work. User can choose which functions to be added to the core while installing. 

[JohnOne]

AutoIt native functions are coded in C++, you cannot just add an AutoIt script to it, they need to be written in C++.

[jvanegmond]

AutoIt native functions are coded in C++, you cannot just add an AutoIt script to it, they need to be written in C++.

AutoIt is boss. It can do anything if you make it do it. Including embedding AutoIt functions internally. Though it wouldn't be too hard to translate AutoIt to C++ -- because all AutoIt internal functions are already there after all. =)

Edited August 13, 2015 by Manadar

[kcvinu]

Then the makers of AutoIt can include it in each upcoming updates. I think these are the most common UDFs 

1. Array.au3 

2. Misc.au3

3. File.au3

4. MsgBoxConstants.au3

5. SQLite.au3

 

[guinness]

How would they include MsgBoxConstants? They are just constants in which you don't have to remember magic values. It would have NO significant performance gain in your code (is this because you hate typing one line?). 

Out of those 5, the one that makes a little bit of sense is the Array UDF.

[kcvinu]

But what about "_IsPressed()" ?. I think it used very commonly. So Misc.au3 is a must. And don't forget about the File.au3 too.

[guinness]

You mean everything in Misc? Come on!

[JohnOne]

I very very rarely use anything in Misc.au3, and even rarer use anything other than _ArrayDisplay in Array.au3

[kcvinu]

Autoit is a scripting language. It is mainly used for automation tasks. So It should have some basic keyboard functions (Like manadar's "HotString") and mouse functions. Without them, what automation  ?. And @guinness I just mentioned _IsPressed only. Sorry for saying Misc.au3

[BrewManNH]

Not everyone uses it for automating tasks in a Window, it's better to do it other ways most of the time. I've never used _IsPressed for anything in something I'm scripting, not sure if I ever would. They're in external UDFs because they don't make sense to put things into the core just because some people want it there, it only makes sense when a majority of people use something, and it makes sense to have it run faster.

[JLogan3o13]

Autoit is a scripting language. It is mainly used for automation tasks. So It should have some basic keyboard functions (Like manadar's "HotString") and mouse functions. Without them, what automation  ?. And @guinness I just mentioned _IsPressed only. Sorry for saying Misc.au3

Something of a blanket statement. 5 years ago I probably would have agreed with it, but I believe AutoIt is rapidly evolving. Simple keyboard and mouse task automation may be the main use you personally have for it, but that doesn't mean it holds true for the entire community.

[kcvinu]

I am not arguing , but AutoIt still lacks better keyboard functions. I mean a function which helps the programmer to do a low level keyboard hook easily. 

[Melba23]

kcvinu,

a function which helps the programmer to do a low level keyboard hook easily

And why do you suppose that is the case? Perhaps this might give you a clue.

And there has always been a reluctance to take further functions into core code as we get enough complaints about the size of the "compiled" executables as it is without further increasing the size of the interpreter which is packaged with each one.

M23

[kcvinu]

@Melba23 And that sounds a very very good reason. Prevention from bloating the compiled exe. 

And i am not talking about key loggers. Just think about a text expander in word or something like that. People needed it. They need to get rid of from repetitive tasks. Typing is a horrible task. take it in a good sense.

[Melba23]

kcvinu,

take it in a good sense

I do, which is why I posted as I did in this thread of yours.

M23