-- Hoogle documentation, generated by Haddock
-- See Hoogle, http://www.haskell.org/hoogle/


-- | Common functionality for bindings-* set of packages.
--   
--   The <tt>bindings-*</tt> set of packages contain low level bindings for
--   established libraries, and is aimed at developers of higher level
--   modules that can use it as foundation. They all mimic the exact names
--   and functionality of the original libraries. For a specific library,
--   look for package <tt>bindings-library_name</tt>.
@package bindings-common
@version 0.1

module Bindings.C
data Timeval
instance Storable Timeval

module Bindings.Utilities
data (Storable a) => GlobalVariable a
setGlobalVariable :: (Storable a) => GlobalVariable a -> a -> IO ()
getGlobalVariable :: (Storable a) => GlobalVariable a -> IO a
class (Storable cb) => Callback cb where { type family F cb :: *; { withCallback f c = do { made <- makeCallback f; result <- c made; freeCallback made; return result } } }
nullCallback :: (Callback cb) => cb
makeCallback :: (Callback cb) => F cb -> IO cb
freeCallback :: (Callback cb) => cb -> IO ()
withCallback :: (Callback cb) => F cb -> (cb -> IO a) -> IO a


-- | <ul>
--   <li>- | Modules under <a>Bindings</a> are supposed to be low level --
--   links to well-known libraries. All of them follow the -- same style
--   for consistency and predictability. Here are -- a few rules that have
--   been followed:</li>
--   <li>- * All packages use cabal. Checking of dependencies is --
--   delegated to <tt>pkg-config</tt> by listing such dependencies -- in
--   cabal file.</li>
--   <li>- * All names are as close as possible to the names in the --
--   original library language. To agree with Haskell case -- conventions
--   they may be prefixed with an underscore or -- have their first letter
--   capitalized.</li>
--   <li>- * Documentation is provided as links to the official -- homepage
--   for a library. Due to the policy of preserving -- names and
--   functionality, such documentation can be used -- as it is.</li>
--   <li>- These modules are supposed to be used by developers of -- higher
--   level modules, who should have a good understanding -- of the undeline
--   libraries they decide to use. Of course, -- you can use them directly
--   if you know what you are doing.</li>
--   </ul>
module Bindings