Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
> Either way, we should make them a WARNING for 7.5, then error in
> 7.6.
Ok, I'll make this change soon.
If we end up marking more 7.5 changes using this mechanism
(i.e. deprecate for 7.5, disallow for 7.6), we could use an #ifdef
symbol to mark all the changes that need to be made permanent for 7.6:
#ifdef 7_5_DEPRECATED_FUNCTIONALITY
...
#endif
Cheers,
Neil
