MacroQuest64

Salutations,
Well, There are two releases out now. Mckorr's release only removes perl, that seems to be the main difference. The official release keeps this. Should we or Should we not keep perl in MQ?

Leave it in -- it's a compile option that is turned off by default. If someone wants it, they can compile it in.

As much as I like perl, I don't see a need for it in MQ. I questioned why AMM was adding it, and got flamed more than answered.

I have not seen perl (in MQ) do anything MQ couldn't do without it.

I voted to remove it, however, since I used MQ for MACROing (normal tradeskills are a pain - literally - without it, wtf was SOE thinking with 150 clicks to make 1 item? Ha! SOE think, right! Anyway I digress.) not SPYing (extended /who etc.) without /click it's useless. Further if /click is to never return perhaps it's time to rename MQ to SQ (SpyQuest)?

I say remove it of course. Helps slim down the code, remove a bunch of extra files, etc.

The other main difference between my version and the official one is that it compile much more easily under VC6, since I've already set all the options and put all the appropriate files in the distro. For example, my source has detours precompiled so you don't need to worry about that step. It also includes a current, correct version of dinput.h, one of the biggest problems for a lot of people.

Has anyone figured out a use for perl in MQ? What would one do with it? In other words, what good is it?

I voted trash it.

Personally, I don't use it, and I'd be shocked if anyone did because everything that I have read has indicated that the MQ/Perl integration code is buggy and can cause MQ to crash.

But, at the same time leaving the code in place hurts nothing. And if someone someday found out a good use for using Perl in their macros and was willing to debug the source code it would be nice to have it all there and in place already.

What many people seem to not understand is that having the Perl files and code in the project does not impact MQ's runtime perfromance one bit. If you don't have USE_PERL defined none of the code will get added to the final .exe or .dll.

My vote is to keep it in.

Personally I dont use PERL and wouldnt mind seeing it ripped out.

But as long as eqlib.cpp is weighing in at 350kb+ and 10k+ lines of code, it will never be "pretty". A redesign splitting the logic out into seperate files etc would be cool imo. But I guess thats a different subject :p