Include A3X file as a script

[anonymous]

I would like to see a way to include compiled scripts in my scripts.

Ex:

#include <myfunclib.a3x> ; my function library in compiled form
#include <otherfunclib.au3> ; other functions, complete with source

I have some function libraries I have written, that represent considerable effort, and in some cases hoop-jumping creativity, to accomplish various tasks. I would like to share these functions with the AutoIt community, but am reluctant to release the source for some of my more creative solutions.

For example, I am finishing a semi-OOP-ish set of functions for basic database functionality, using AutoIt3 native commands/functions only (no COM dependencies). From what I've read in the forums, I know there are several people that would benefit from being able to use this.

There are probably more UDFs out there that scripters are reluctant to share because they do not want to just give away their most creative code, that they might share if they could just distribute a compiled library.

I can also see this as a benefit if I contract to write some AU3 scripts for a client that wants the code for those scripts, but needs to have one of my functions included. By including a compiled function library script, they can have the code that was written specifically for them on their dime, but still benefit from more advanced functions I have written and want to keep control over.

[TicketCleanup]

Automatic ticket cleanup.

[Valik]

I've changed your summary to be a little more explicit. Really all you're asking for is the ability to #include A3X compiled files as if they were raw source. That's something I've always wanted as well.

[anonymous]

Would the more generic nature of the original ticket summary be entirely out of the question? That is, would it be impossible to also allow compiled EXE files to be included as well? (Naturally, the only EXEs that would work would be those compiled scripts that are not UPX'd)

The rationale behind this is that I have a compiled executable whose functionality I'm considering allowing users to extend via their own scripts. I could always distribute an A3X file and have them download AutoIt (or maybe even do some FileInstall procdedure), but then that quickly becomes very clunky, especially when I make use of custom icon resources added to the executable directly.

[Valik]

There are much much better ways of going about that than what you suggest. The "correct" way is to establish some sort of inter-process communication. Then provide a library file with an API plugins can use in their plugin-script to interact with the main program.

In short, AutoIt can not help you with what you want to do. Your suggestion makes no sense and does not solve the problem you wish to solve.

[willi_chan@…]

As the original poster, let me say that I do not think that including an exe would be practical, but either an A3X, or some new compiled form that includes function interfaces is needed. I am also working on some scripts that create and use keycode files to handle scritps that need to include authentication, but I cannot share the scripts or allow anyone else to use the routines without negating the security. The ability to include compiled function libraries becomes more and more necessary with each project I take on.

[anonymous]

is doing?

[trancexx]

Added by revision [7035] in version: 3.3.9.5