bindings-common 0.1.1 → 0.1.2

raw patch · 3 files changed

+26/−25 lines, 3 filesPVP ok

version bump matches the API change (PVP)

API changes (from Hackage documentation)

Files

• bindings-common.cabal +1/−1
• src/Bindings.hs +19/−19
• src/Bindings/Utilities.hs +6/−5

@@ -9,7 +9,7 @@   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 @bindings-library_name@.-version: 0.1.1+version: 0.1.2 license: BSD3 license-file: LICENSE maintainer: Maurício C. Antunes

@@ -1,28 +1,28 @@ {-| -    -- | Modules under "Bindings" 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:+    | Modules under "Bindings" 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: -    -- * All packages use cabal. Checking of dependencies is-    -- delegated to @pkg-config@ by listing such dependencies-    -- in cabal file.+    * All packages use cabal. Checking of dependencies is+    delegated to @pkg-config@ by listing such dependencies+    in cabal file. -    -- * 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.+    * 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. -    -- * 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.+    * 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. -    -- 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.+    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.  -} 

@@ -36,8 +36,7 @@      type F cb :: * -    -- | 'nullCallback' can be used like 'Foreign.Ptr.nullPtr'-    -- or 'Foreign.Ptr.nullFunPtr'.+    -- | 'nullCallback' can be used like 'Foreign.Ptr.nullFunPtr'.      nullCallback :: cb @@ -47,9 +46,11 @@      makeCallback :: F cb -> IO cb -    -- | 'freeCallback' should be called on all members-    -- of a foreign function type after they-    -- are no longer going to be used.+    -- | 'freeCallback' should be called on all values returned+    -- by 'makeCallback' after they are no longer going to be+    -- used. Most of the time this class method will just use+    -- 'Foreign.Ptr.freeHaskellFunPtr'.  of a foreign function+    -- type after they are no longer going to be used.      freeCallback :: cb -> IO ()