Procedure for obsoleting Lua Functions
#4
(01-21-2014, 05:07 PM)xoft Wrote: Usually we try to keep stuff as-is by providing manual bindings, and putting a LOGWARN in them saying that the function is obsolete and to use XYZ as replacement. Of course that's the best case scenario Smile

Putting an OBSOLETE modifier in front of function doesn't work so well for Lua, because it doesn't inform plugins that they're using obsolete stuff, but it creates warnings when compiling the MCS executable. The OBSOLETE modifier is meant for internal C++ code, not for API.

That's exactly what I wanted to know. In most cases I should be able to write a forwarding function that does the warning and then the call.
Reply
Thanks given by:


Messages In This Thread
RE: Procedure for obsoleting Lua Functions - by worktycho - 01-22-2014, 03:16 AM



Users browsing this thread: 1 Guest(s)