suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ffi/unsafe/objc docs: clarification on `import-class'

Browse Source 
Merge to v5.3.2
(cherry picked from commit 2adf0bdf2e)
This commit is contained in:
Matthew Flatt 2013-01-13 15:30:38 -07:00 committed by Ryan Culpepper
parent 48380b48c2
commit d450ff94cb
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
collects/scribblings/foreign/objc.scrbl
View File

@ -107,6 +107,23 @@ Defines each @racket[class-id] to the class (a value with FFI type
@examples[ @examples[
#:eval objc-eval #:eval objc-eval
(eval:alts (import-class NSString) (void)) (eval:alts (import-class NSString) (void))
]
A class accessed by @racket[import-class] is normally declared as a
side effect of loading a foreign library. For example, if you want to
import the class @tt{NSString} on Mac OS X, the @filepath{Foundation}
framework must be loaded, first. Beware that if you use
@racket[import-class] in DrRacket or a module that @racket[require]s
@racketmodname[racket/gui/base], then @filepath{Foundation} will have
been loaded into the Racket process already. To avoid relying on other
libraries to load @filepath{Foundation}, explicitly load it with
@racket[ffi-lib]:
@examples[
#:eval objc-eval
(eval:alts (ffi-lib
"/System/Library/Frameworks/Foundation.framework/Foundation") (void))
(eval:alts (import-class NSString) (void))
]} ]}
@defform[(import-protocol protocol-id ...)]{ @defform[(import-protocol protocol-id ...)]{