Hi Tony, > On Sun, Aug 26, 2012 at 6:31 PM, Tony Garnock-Jones <<a href="mailto:tonyg@ccs.neu.edu">tonyg@ccs.neu.edu</a>> wrote: > > Hi Juan, > > On 2012-08-26 1:10 PM, Juan Garcia wrote: > > I'm having a problem wrapping the Rabbit MQ C client > > library (<a href="https://github.com/alanxz/rabbitmq-c">https://github.com/alanxz/rabbitmq-c</a>) using the ffi. My > > problem is with the amqp_queue_declare function. [...] > > While I don't immediately see the problem with your FFI interface to > librabbitmq, I'd like to point out that it's a very low-level library, > and so is quite difficult to use. If there's nothing AMQP-specific about > your messaging needs, I recommend enabling the RabbitMQ STOMP > server-side adapter and using (require (planet tonyg/stomp)). > > The main advantage is that the pure-Racket implementation of the client > side of the protocol means no SIGSEGVs, no shared-library dependencies, > and cross-platform support. ... I like the look of your library, and I will be using it to interface with RabbitMQ. Having said that, I'd still like to know what I'm doing wrong with my ffi-code. I have a couple of libraries I still need to wrap to complete my project. Thanks for the reply. Regards,