Thanks, Christiaan 

Does it mean that GLFW-b and GLFW (haskell package) are not meant to be used together?

I like some GLFW-b functionality, but I also like to be able to call some of GLFW haskell package functions.  If I try to import GLFW-b and GLFW at the same time - I get the 'ambigous name' error.  Is there a recommendation for a good coding practice here?

Regards,

Vladimir

On 12 December 2013 10:35, Christiaan Baaij <christiaan.baaij@gmail.com> wrote:

The GLFW and GLFW-b package on hackage are _both_ wrappers around the C-library GLFW.
So, GLFW-b "extends" the GLFW C-library, _not_ the GLFW haskell package.

Hope everything is clear now.

-- Christiaan

On Dec 12, 2013, at 9:42 AM, Vlad Lopatin <madjestic13@gmail.com> wrote:

> Hey guys,
>
> I am messing with OpenGL and here's the question:
>
> GLFW-b is supposed to be based on GLFW and extend it.  How come GLFW-b naming is ambiguous with GLFW?  GLFW-b main module is named the same as GLFW (import Graphics.UI.GLFW), making it necessary to hide one of the libraries via ghc-pkg hide, or to use a language extension in order to solve ambiguity.  I am tempted to consider it a bug, unless somebody knows a good reason for it to be called a feature.
>
> Am I missing something?
>
> Regards,
> Vladimir

> _______________________________________________
> Haskell-Cafe mailing list
> Haskell-Cafe@haskell.org
> http://www.haskell.org/mailman/listinfo/haskell-cafe

_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe