1. You're probably aware of this, but as I was re-learning some of the examples in the book for practice, I kept running into really stupid problems. Then, I figured out that the main problem was that the function message() no longer works!

    http://www.wowwiki.com/API_message "As of 3.2 message() is broken / Depreciated as the message frame is no longer defined. Suitable Alternative is print"

    A lot of the basic examples in the book use message(), and I didn't see anywhere on the website mentioning this, so I figured I'd post this just in case! (Also, in case anyone else has the same problem!)

    Thanks for the great book! Conexion

    You're probably aware of this, but as I was re-learning some of the examples in the book for practice, I kept running into really stupid problems. Then, I figured out that the main problem was that the function message() no longer works!

    Yes, that function has been removed and is no longer listed in our API listing. In addition, our docuementation (as of yesterday) shows a warning message when you go to a function that is no longer valid in the current version of WoW.

    http://www.wowwiki.com/API_message "As of 3.2 message() is broken / Depreciated as the message frame is no longer defined. Suitable Alternative is print"

    A lot of the basic examples in the book use message(), and I didn't see anywhere on the website mentioning this, so I figured I'd post this just in case! (Also, in case anyone else has the same problem!)

    Not all that many examples use message() actually, since we provide WowLua and encouraged the use of print() there, even before it existed in vanilla WoW. The code is being updated for the second edition, but if you give me the information about where it's telling you to use message, Ill ensure its added to that chapter's errata.

    No problem!

    Part 3 - Chapter 16 - Page 234 (Writing an Addon Without XML)

    Part 2 - Chapter 8 - Page 110 (Programming Within World of Warcraft)