On 2010/12/17 05:49, mattschinkel wrote:
Adding a 'deprecated' warning would affect other jallib samples. Our group does not allow any warnings, so build bot would fail.
Indeed, the Jallib material should be warning-free. This implies that we would need to update the libraries and samples affected by such an API change. That is an unavoidable consequence, but something we have under control.
All I wanted to say is: there is no dogma that says "thou shall not change the API". There may be good reasons for such a change! But for the user we can reduce the effect of such a change with an 'alias' function. The 'deprecated' warning is solely to encourage the user to migrate his application to the new standard.
Regards, Rob. -- R. Hamerling, Netherlands --- http://www.robh.nl -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
