Should we remove perl entirely?
Moderator: MacroQuest Developers
I've been voting to have it pulled out for a while. Changes to both EQ and MQ past and present make it outdated.
I understand folks were using it to call external programs such as Winamp and ShowEQ, but EQ has a built in player, and the new mapping system makes ShowEQ unnecessary for the basic user. I'm sure there are other things it can be used for, but the MQ scripting language has evolved to the point where additional, external scripting doesn't seem terrible necessary.
Perhaps we should consider rebuilding MQ a bit to allow plugins. That way folks could develop a PERL plugin, etc. if they wanted it. Not sure how feasible this is considering the current integrated state of the PERL calls in the source code.
I understand folks were using it to call external programs such as Winamp and ShowEQ, but EQ has a built in player, and the new mapping system makes ShowEQ unnecessary for the basic user. I'm sure there are other things it can be used for, but the MQ scripting language has evolved to the point where additional, external scripting doesn't seem terrible necessary.
Perhaps we should consider rebuilding MQ a bit to allow plugins. That way folks could develop a PERL plugin, etc. if they wanted it. Not sure how feasible this is considering the current integrated state of the PERL calls in the source code.
MQ2: Think of it as Evolution in action.
/shrug
It never bothered me in coding and I always like having features around even if I don't use it. Hell, I remember when someone was bound and determined to remove the Telnet session option from the program a few months ago!
We're not to the point of code bloat, in my opinion. Although, stuff that is broken that will always be broken due to new SOE code, should be nixed.
Actually, a re-write of the parser system would be more helpful to reading through code than anything else ..hehe. Although what a hell of a job that would be ..hehe ...was bad enough just splitting EQLib.cpp up in the first place.
It never bothered me in coding and I always like having features around even if I don't use it. Hell, I remember when someone was bound and determined to remove the Telnet session option from the program a few months ago!
We're not to the point of code bloat, in my opinion. Although, stuff that is broken that will always be broken due to new SOE code, should be nixed.
Actually, a re-write of the parser system would be more helpful to reading through code than anything else ..hehe. Although what a hell of a job that would be ..hehe ...was bad enough just splitting EQLib.cpp up in the first place.