Jump to content

Embedding live Perl code into AutoIt3


thomasl
 Share

Recommended Posts

(I recently posted this bit over in the Scripts and Scraps forum but it seems that here would be a more appropriate place as it's not really a script.)

I have stitched together an interface library (basically a DLL) to embed live Perl code into AU3 scripts. More details and a fully working package, including all source code, an example and the Perl DLL itself (which means there's no need to install Perl), are here: http://thomaslauer.com/comp/Calling_Perl

See also this thread in Scripts and Scraps.

Link to comment
Share on other sites

(I recently posted this bit over in the Scripts and Scraps forum but it seems that here would be a more appropriate place as it's not really a script.)

I have stitched together an interface library (basically a DLL) to embed live Perl code into AU3 scripts. More details and a fully working package, including all source code, an example and the Perl DLL itself (which means there's no need to install Perl), are here: http://thomaslauer.com/comp/Calling_Perl

See also this thread in Scripts and Scraps.

Hello, Tomasl!

Thank you for your Perl's DLL.

Would you like to be member of AutoItList group on Yahoo?

http://tech.groups.yahoo.com/group/autoitlist/

It will be great to read about your zillion ideas. This group has above 4000 members - AutoIt lovers from day of it's creation - more than 30,000 messages.

Sincerely,

Valery Ivanov

PS I registered here specially for this message, only.

Link to comment
Share on other sites

cant perlxx.dll be called directly?

Of course it can. In theory, what the C code does could be done with some well-crafted AU3 code as well.

In practice, it's not that easy. There are a number of reasons why I decided against direct calls to PERLxx.DLL from AU3:

  • it would not be as portable as using the macros #define'd in PERL.H for exactly that purpose
  • it's more complicated and pretty error-prone
  • it has no intrinsic advantages as the ultimate calls are routed to a DLL anyway; whether you install one or two DLLs doesn't make much of a difference (well, not to me anyway: I did this mainly for my own purposes)
However, my C code is in the public domain for a reason; you're more than welcome to translate it into AU3. The obvious starting point would be the mess the C preprocessor produces (not what I'd call a pretty sight, but there you are).

If you or anyone else wants to travel down that stony road, PM me and I can give you some more pointers.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...