From 82ba818ff456bcd6d56a06226e3f27e98fbb55c3 Mon Sep 17 00:00:00 2001
From: Craig Jennings <c@cjennings.net>
Date: Thu, 14 Aug 2025 22:58:58 -0500
Subject: removing all downloaded devdocs files

---
 devdocs/gcc~13/messaging-with-the-gnu-objective-c-runtime.html | 6 ------
 1 file changed, 6 deletions(-)
 delete mode 100644 devdocs/gcc~13/messaging-with-the-gnu-objective-c-runtime.html

(limited to 'devdocs/gcc~13/messaging-with-the-gnu-objective-c-runtime.html')

diff --git a/devdocs/gcc~13/messaging-with-the-gnu-objective-c-runtime.html b/devdocs/gcc~13/messaging-with-the-gnu-objective-c-runtime.html
deleted file mode 100644
index 84f4b828..00000000
--- a/devdocs/gcc~13/messaging-with-the-gnu-objective-c-runtime.html
+++ /dev/null
@@ -1,6 +0,0 @@
-<div class="section-level-extent" id="Messaging-with-the-GNU-Objective-C-runtime"> <div class="nav-panel"> <p> Previous: <a href="fast-enumeration" accesskey="p" rel="prev">Fast Enumeration</a>, Up: <a href="objective-c" accesskey="u" rel="up">GNU Objective-C Features</a> [<a href="index#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="indices" title="Index" rel="index">Index</a>]</p> </div>  <h1 class="section" id="Messaging-with-the-GNU-Objective-C-Runtime"><span>8.10 Messaging with the GNU Objective-C Runtime<a class="copiable-link" href="#Messaging-with-the-GNU-Objective-C-Runtime"> ¶</a></span></h1> <p>This section is specific for the GNU Objective-C runtime. If you are using a different runtime, you can skip it. </p> <p>The implementation of messaging in the GNU Objective-C runtime is designed to be portable, and so is based on standard C. </p> <p>Sending a message in the GNU Objective-C runtime is composed of two separate steps. First, there is a call to the lookup function, <code class="code">objc_msg_lookup ()</code> (or, in the case of messages to super, <code class="code">objc_msg_lookup_super ()</code>). This runtime function takes as argument the receiver and the selector of the method to be called; it returns the <code class="code">IMP</code>, that is a pointer to the function implementing the method. The second step of method invocation consists of casting this pointer function to the appropriate function pointer type, and calling the function pointed to it with the right arguments. </p> <p>For example, when the compiler encounters a method invocation such as <code class="code">[object init]</code>, it compiles it into a call to <code class="code">objc_msg_lookup (object, @selector(init))</code> followed by a cast of the returned value to the appropriate function pointer type, and then it calls it. </p> <ul class="mini-toc"> <li><a href="dynamically-registering-methods" accesskey="1">Dynamically Registering Methods</a></li> <li><a href="forwarding-hook" accesskey="2">Forwarding Hook</a></li> </ul> </div><div class="_attribution">
-  <p class="_attribution-p">
-    &copy; Free Software Foundation<br>Licensed under the GNU Free Documentation License, Version 1.3.<br>
-    <a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Messaging-with-the-GNU-Objective-C-runtime.html" class="_attribution-link">https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Messaging-with-the-GNU-Objective-C-runtime.html</a>
-  </p>
-</div>
-- 
cgit v1.2.3