(mailing list in CC, for the reasons Danny mentioned) Searching PLaneT [1], I've just found Dave Herman's package which may be of interest to you: http://planet.racket-lang.org/display.ss?package=c.plt&owner=dherman
Never tried it, not sure it's what you want, but should be worth trying. If you do try it, please report back! Laurent [1] http://planet.racket-lang.org/ On Wed, May 29, 2013 at 7:43 AM, maxwell <maxw...@partyvan.info> wrote: > Is there no function similar to get-ffi-obj that allows you to just grab a > struct from a library? It seems like a pretty integral feature, why can't > such a function exist as part of the FFI? > > > On Tue, May 28, 2013 at 12:31 AM, Laurent <laurent.ors...@gmail.com>wrote: > >> Most of the time, you won't need all the features of the struct. >> For pointers you don't care about, you can simply use the generic >> _pointer type, as long as you don't use the /types/ behind that pointer. >> Note that you can still use the pointer itself though, e.g., to pass it >> around functions. >> >> And if for some reason at some point in time you need the struct >> definition of that pointer, you can "expand" the definitions of your struct >> types a little. >> >> HTH >> Laurent >> >> >> >> On Tue, May 28, 2013 at 9:09 AM, Danny Yoo <d...@hashcollision.org>wrote: >> >>> >>> >>> On Monday, May 27, 2013, maxwell wrote: >>> >>>> Hello Doctor Yoo, >>>> >>>> I am having serious problems with the Racket FFI. Apparently, to load a >>>> struct from a library, I have to know all of it's contents, and then define >>>> them in terms of their contents, until everything has been defined in terms >>>> of C primitives. Surely I am incorrect. Can you explain this to me? What do >>>> I do if the struct I need has 200 struct pointers in it, each of which >>>> points to 200 more, and so on, a couple of layers deep? >>>> >>>> I am sorry to bother you with this but I am going insane and I need to >>>> sleep, but this is keeping me up! >>>> >>>> - Maxwell >>>> >>> >>> >>> Hi Maxwell, >>> >>> I'm forwarding this to the Racket-lang mailing list. Typically, it is >>> better to ask communities for support rather than single people, to reduce >>> dependence on one point of failure. >>> >>> >>> >>> >>> >>> ____________________ >>> Racket Users list: >>> http://lists.racket-lang.org/users >>> >>> >> >
____________________ Racket Users list: http://lists.racket-lang.org/users
