LISP was just the first thing that came to mind when trying to think of a more simple scripting language, something closer to plain English. I wasn't thinking of replacing PERL with LISP. We just need a simpler syntax. All them strange variables get confusing late at night.
Investigating Dev-C++ now to see how the IDE looks, but if y'all want to stick with VC++ so be it... but how 'bout we use 6.0 instead of .NET? Seems from the various posts here that most folks have or have access to 6.0, and very few to a full version of .NET. I'm guessing Plaz works in the IT field and so had access to it without spending a couple hundred bucks... which would also explain why he implemented PERL.
Either way PERL should go, so we don't have to worry about PERL and Non-PERL versions and compiles. The non-PERL version just gave me fits anyway once Plaz incorporated PERL into MQ :)
Not sure about plugin DLL's. I write a lot of my macros with #includes to keep from rewriting or cutting and pasting code. Currently MQ doesn't handle this in a very robust fashion. Passing variables to included subroutines can be a pain, and events don't carry across to an #included file since they are declared outside the "sub Main" loop, which appears to be where a called external function begins execution. I'd like to see a better implementation of the whole function.
L124RD's MacroKit is a good example of what you can do with #include. In fact I use it quite a bit to simplify my melee and autohunting scripts. Try this in a hotkey:
Code: Select all
#include routines.mac
#include macrokit.inc
sub Main
/call Melee
/endmacro
And never have to press that annoying Bash, Kick, etc. hotkey again once you have a target in your sights.
Expanding on the #include function would allow a much easier exchange of code snippets. Macros then become modularized:
Code: Select all
#include routines.[color=red]inc[/color]
#include melee.inc
#include health.inc
sub Main
:loop
/if $char(hp.pct) < 50 /call Healme
else /call Fight
/goto loop
/endmacro
Melee.inc would define fighting routines for melee classes, and Health.inc would take into account sitting, binding, healing spells, etc. New macros wouldn't require rewriting those routines, and events would be handled by the external modules instead of being declared in the main macro.
Sorry if I'm rambling, been up since 3am. You know the Army: "We waste more time before 9am than most people waste all day."
One question I did have: How many of us are using DX9 instead of the 8.1 EQ requires, and what impact does this have on the code?
). GCC 3.2 is free (well, GNU Public License), as is the WinAPI environment Dev-C++ (available on Sourceforge, http://sourceforge.net/projects/dev-cpp/).
