Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Separating the language from the backend

Started by Guest , Jul 16 2012 03:14 PM

Please log in to reply

6 replies to this topic

#1 Guests

Guests

Posted 16 July 2012 - 03:14 PM

Would it be hard to do? There should be an AHK library and the actual language should only be a wrapper around this library, so that any other language could be used to program AHK scripts for which a wrapper is written.

Is it planned? It would make much more sense to make the backend independent of the language, because then mature languages (e.g. Python) could be used for writing the scripts.

Back to top

#2 Guests

Guests

Posted 16 July 2012 - 04:43 PM

Same guest as in the past who suggested in a number of times before such as here <a class="postlink-local" href="http://www.autohotkey.com/community/viewtopic.php?p=390666">viewtopic.php?p=390666</a> :?:

Back to top

#3 Carcophan

Members
1568 posts

Posted 16 July 2012 - 08:21 PM

Would it be hard to do? There should be an AHK library and the actual language should only be a wrapper around this library, so that any other language could be used to program AHK scripts for which a wrapper is written.

Is it planned? It would make much more sense to make the backend independent of the language, because then mature languages (e.g. Python) could be used for writing the scripts.

I am not the brightest lightbulb really, but why would you use Python to code AHK... when you can just use AHK to code AHK?

You want to be able to use all of AHK's functionality, without learning the actual syntax?

Back to top

#4 fragman

Members
1591 posts

Posted 17 July 2012 - 04:23 PM

Would it be hard to do? There should be an AHK library and the actual language should only be a wrapper around this library, so that any other language could be used to program AHK scripts for which a wrapper is written.

Is it planned? It would make much more sense to make the backend independent of the language, because then mature languages (e.g. Python) could be used for writing the scripts.

I am not the brightest lightbulb really, but why would you use Python to code AHK... when you can just use AHK to code AHK?

You want to be able to use all of AHK's functionality, without learning the actual syntax?

There are many other possible benefits, such as availability of certain modules.

Back to top

#5 Carcophan

Members
1568 posts

Posted 17 July 2012 - 06:41 PM

There are many other possible benefits, such as availability of certain modules.

I guess I don't understand why that is relavent though.

So, a 'module' that is only available for python, would be called and usable through AHK?

But why. Can anyone give a psudo-example to better put this into context for me?

Back to top

#6 fragman

Members
1591 posts

Posted 17 July 2012 - 09:01 PM

There are many other possible benefits, such as availability of certain modules.

I guess I don't understand why that is relavent though.

So, a 'module' that is only available for python, would be called and usable through AHK?

But why. Can anyone give a psudo-example to better put this into context for me?

No, the other way around. Users could use Python (which has much more advanced modules than most AHK libraries) and still profit from the functionality of AHK (working with windows, hotkeys, etc. where Python might fall short). There are some attempts in this direction, namely Autohotkey.dll, but a proper separation between the language and AutoHotkey features would be better.