in reply to Re: Binding C libraries
in thread Binding C libraries
Generally, the design is specific to the application. Use the most suitable tool for the job ! If all you're writing is a set of list utilities, for example, no object orientation is *really* needed. In some designs, however, there really is a place for objects.
One of the most important things to keep in mind about this is that a library is better to be "stateless". This allows to write multi-threaded code with no problems. Object oriented programming in Perl (passing $self around) is stateless if done right. Writing a C library with a bunch of static objects and functions that act upon them is far from being stateless, however, and if such a thing is absolutely required don't forget to document it.
|
|---|