From: Jonathan Roelofs Date: Mon, 12 Sep 2016 16:14:52 +0000 (+0000) Subject: Trivial documentation fix regarding Obj-C ARC objc_arc_weak_reference_unavailable X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=96cb94b2a9286f27dfb1de9dc8ba814f8958e177;p=platform%2Fupstream%2Fllvm.git Trivial documentation fix regarding Obj-C ARC objc_arc_weak_reference_unavailable Fixed incorrect docs that referred to: objc_arc_weak_unavailable when it should be: objc_arc_weak_reference_unavailable Patch by: Sean McBride! llvm-svn: 281227 --- diff --git a/clang/docs/AutomaticReferenceCounting.rst b/clang/docs/AutomaticReferenceCounting.rst index 2faed23..aa2a283 100644 --- a/clang/docs/AutomaticReferenceCounting.rst +++ b/clang/docs/AutomaticReferenceCounting.rst @@ -910,10 +910,10 @@ not support ``__weak`` references. binary compatibility. A class may indicate that it does not support weak references by providing the -``objc_arc_weak_unavailable`` attribute on the class's interface declaration. A +``objc_arc_weak_reference_unavailable`` attribute on the class's interface declaration. A retainable object pointer type is **weak-unavailable** if is a pointer to an (optionally protocol-qualified) Objective-C class ``T`` where -``T`` or one of its superclasses has the ``objc_arc_weak_unavailable`` +``T`` or one of its superclasses has the ``objc_arc_weak_reference_unavailable`` attribute. A program is ill-formed if it applies the ``__weak`` ownership qualifier to a weak-unavailable type or if the value operand of a weak assignment operation has a weak-unavailable type.