RAMzor Posted June 7, 2010 Share Posted June 7, 2010 Hi! Is it possible to automatically convert my script(s) from V3.3.0.0 to V3.3.2.0 and newer Thanks in advance. Link to comment Share on other sites More sharing options...
PsaltyDS Posted June 7, 2010 Share Posted June 7, 2010 In a word, NO. You would have to script a parser to go through every line of a script, finding everything mentioned in the change logs between 3.3.0.0 and 3.3.2.0 and correctly change it (i.e. AdLibRegister() vice AdLibEnable()). Sounds very painful, but hey, that's why you make the big scripting bucks! Valuater's AutoIt 1-2-3, Class... Is now in Session!For those who want somebody to write the script for them: RentACoder"Any technology distinguishable from magic is insufficiently advanced." -- Geek's corollary to Clarke's law Link to comment Share on other sites More sharing options...
RAMzor Posted June 7, 2010 Author Share Posted June 7, 2010 Thanks man! Link to comment Share on other sites More sharing options...
GEOSoft Posted June 7, 2010 Share Posted June 7, 2010 You might also want to read this. http://www.autoitscript.com/forum/index.php?showtopic=70902 George Question about decompiling code? Read the decompiling FAQ and don't bother posting the question in the forums.Be sure to read and follow the forum rules. -AKA the AutoIt Reading and Comprehension Skills test.*** The PCRE (Regular Expression) ToolKit for AutoIT - (Updated Oct 20, 2011 ver:3.0.1.13) - Please update your current version before filing any bug reports. The installer now includes both 32 and 64 bit versions. No change in version number. Visit my Blog .. currently not active but it will soon be resplendent with news and views. Also please remove any links you may have to my website. it is soon to be closed and replaced with something else. "Old age and treachery will always overcome youth and skill!" Link to comment Share on other sites More sharing options...
Anteaus Posted June 7, 2010 Share Posted June 7, 2010 You would have to script a parser to go through every line of a script, finding everything mentioned in the change logs between 3.3.0.0 and 3.3.2.0 and correctly change it (i.e. AdLibRegister() vice AdLibEnable()). A simpler workaround is a script (or just a batchfile) which allows you to select the compiler for a given job. Another way to do this (on NTFS) is to define an "autoit" junction which points to the required interpreter/compiler, and change this as required. That way, the debugging tools should work pretty-much the same for each. I'm still using 3.2 for some work. Mainly because some of the effects are subtle, and a version-change calls-for a VERY thorough retest to make sure there aren't obscure problems. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now