|
AceComm and message()
I ran into a problem with a conflict with Cartographer, specially its use of AceComm, and an addon I maintain.
The problem turns out the AceComm:SendCommMessage() function uses a variable called "message" without declaring it first as local. (The variable name "message" is extensively used through AceComm, and the code is usually its pretty good about "local"ing it.)
Unfortunately, message is already declared by Blizzard as a function to display a dialog box, and is heavily used through the internal WoW addons, as well as a few third-party addons such as my own.
When SendCommMesssage runs, message() gets redefined as a table since there is no "local" declaration of it first. Not good.
The Ace maintainer(s) might want to add a "local message" declaration to this function and check the rest library for other like problems.
|
Linear Mode
