Thank you for response. I already sent another patch, it could be found here: http://article.gmane.org/gmane.comp.compilers.clang.scm/114023
-- AlexDenisov Software Engineer, https://github.com/AlexDenisov On 5 Jan 2015 at 19:39:16, jahanian ([email protected]) wrote: On Dec 24, 2014, at 3:29 AM, AlexDenisov <[email protected]> wrote: Do the usual lookup to find the method which implements this syntax. Call Decl::getAvailability on this method. If it returns anything other than AvailabilityResult::AR_Available Well, I understand this part, it’s pretty obvious. But what I don’t understand is: issue an appropriate diagnostic. What is appropriate diagnostic for AR_NotYetIntroduced? Should I introduce this diagnostic? Or just show warning/error for Deprecated/Unavailable and ignore NotYetIntroduced AR? It is sufficient to issue an unavailability diagnostics since diagnostic points to the method which has the availability info. as part of its declaration. - Fariborz
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
