doc typo fixes from Eric Hanchrow
This commit is contained in:
parent
9924ac8060
commit
2c0a034792
|
@ -4,7 +4,7 @@
|
|||
@title[#:tag "intro"]{Overview}
|
||||
|
||||
Although using the FFI requires writing no new C code, it provides
|
||||
very little insulation against the issues that C programmer faces
|
||||
very little insulation against the issues that C programmers face
|
||||
related to safety and memory management. An FFI programmer must be
|
||||
particularly aware of memory management issues for data that spans the
|
||||
Racket--C divide. Thus, this manual relies in many ways on the
|
||||
|
|
|
@ -19,7 +19,7 @@ Returns @scheme[#t] if @scheme[v] is the result of @scheme[ffi-lib],
|
|||
@defproc[(ffi-lib [path (or/c path-string? #f)]
|
||||
[version (or/c string? (listof (or/c string? #f)) #f) #f]) any]{
|
||||
|
||||
Returns an foreign-library value. If @scheme[path] is a path, the
|
||||
Returns a foreign-library value. If @scheme[path] is a path, the
|
||||
result represents the foreign library, which is opened in an
|
||||
OS-specific way (using @cpp{LoadLibrary} under Windows, and
|
||||
@cpp{dlopen} under Unix and Mac OS X).
|
||||
|
|
Loading…
Reference in New Issue
Block a user