Name Description Size
declare.rs ! Functionality for declaring Objective-C classes. Classes can be declared using the `ClassDecl` struct. Instance variables and methods can then be added before the class is ultimately registered. # Example The following example demonstrates declaring a class named `MyNumber` that has one ivar, a `u32` named `_number` and a `number` method that returns it: ``` no_run # #[macro_use] extern crate objc; # use objc::declare::ClassDecl; # use objc::runtime::{Class, Object, Sel}; # fn main() { let superclass = class!(NSObject); let mut decl = ClassDecl::new("MyNumber", superclass).unwrap(); // Add an instance variable decl.add_ivar::<u32>("_number"); // Add an ObjC method for getting the number extern fn my_number_get(this: &Object, _cmd: Sel) -> u32 { unsafe { *this.get_ivar("_number") } } unsafe { decl.add_method(sel!(number), my_number_get as extern fn(&Object, Sel) -> u32); } decl.register(); # } ``` 11647
encode.rs 7572
exception.rs 268
lib.rs ! Objective-C Runtime bindings and wrapper for Rust. # Messaging objects Objective-C objects can be messaged using the [`msg_send!`](macro.msg_send!.html) macro: ``` no_run # #[macro_use] extern crate objc; # use objc::runtime::{BOOL, Class, Object}; # fn main() { # unsafe { let cls = class!(NSObject); let obj: *mut Object = msg_send![cls, new]; let hash: usize = msg_send![obj, hash]; let is_kind: BOOL = msg_send![obj, isKindOfClass:cls]; // Even void methods must have their return type annotated let _: () = msg_send![obj, release]; # } # } ``` # Reference counting Utilities for reference counting Objective-C objects are provided in the [`rc`](rc/index.html) module. # Declaring classes Objective-C classes can even be declared from Rust using the functionality of the [`declare`](declare/index.html) module. # Exceptions By default, if the `msg_send!` macro causes an exception to be thrown, this will unwind into Rust resulting in unsafe, undefined behavior. However, this crate has an `"exception"` feature which, when enabled, wraps each `msg_send!` in a `@try`/`@catch` and panics if an exception is caught, preventing Objective-C from unwinding into Rust. # Message type verification The Objective-C runtime includes encodings for each method that describe the argument and return types. This crate can take advantage of these encodings to verify that the types used in Rust match the types encoded for the method. To use this functionality, enable the `"verify_message"` feature. With this feature enabled, type checking is performed for every message send, which also requires that all arguments and return values for all messages implement `Encode`. If this requirement is burdensome or you'd rather just verify specific messages, you can call the [`Message::verify_message`](trait.Message.html#method.verify_message) method for specific selectors. # Support for other Operating Systems The bindings can be used on Linux or *BSD utilizing the [GNUstep Objective-C runtime](https://www.github.com/gnustep/libobjc2). 2607
macros.rs Gets a reference to a `Class`. Panics if no class with the given name can be found. To check for a class that may not exist, use `Class::get`. # Example ``` no_run # #[macro_use] extern crate objc; # fn main() { let cls = class!(NSObject); # } ``` 4712
message
rc
runtime.rs A Rust interface for the functionality of the Objective-C runtime. For more information on foreign functions, see Apple's documentation: <https://developer.apple.com/library/mac/documentation/Cocoa/Reference/ObjCRuntimeRef/index.html> 20678
test_utils.rs 5522