ANN: Haskell BLAS bindings version 0.7

Here's the haddock documentation; I'm not sure if Hackage honors {-# OPTIONS_HADDOCK hide #-} when it displays the exposed modules: http://quantile95.com/blas/ Patrick

2009/1/10 Patrick Perry
Here's the haddock documentation; I'm not sure if Hackage honors {-# OPTIONS_HADDOCK hide #-} when it displays the exposed modules:
It should, so If it doesn't then please tell us about it. We have a trac at: http://trac.haskell.org/haddock/ David

Hi David, The problem is with Hackage, not with haddock. Patrick On Jan 10, 2009, at 3:38 AM, David Waern wrote:
2009/1/10 Patrick Perry
: Here's the haddock documentation; I'm not sure if Hackage honors {-# OPTIONS_HADDOCK hide #-} when it displays the exposed modules:
It should, so If it doesn't then please tell us about it. We have a trac at:
http://trac.haskell.org/haddock/
David

The reason I want to expose modules but hide the documentation is because there are a lot of "unsafeX" functions I want to provide access to, but which 99% of users don't care about. The array library does the same thing. Patrick

Why don't you put them into a separate non-hidden Unsafe module and
provide documentation for it? Users who don't care simply won't look
there, whereas users who do care (for whom you are providing access)
will still have a possibility to do so.
2009/1/10 Patrick Perry
The reason I want to expose modules but hide the documentation is because there are a lot of "unsafeX" functions I want to provide access to, but which 99% of users don't care about. The array library does the same thing.
Patrick
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

Thanks for the suggestion! Done and uploaded to hackage. Patrick On Jan 10, 2009, at 9:07 AM, Eugene Kirpichov wrote:
Why don't you put them into a separate non-hidden Unsafe module and provide documentation for it? Users who don't care simply won't look there, whereas users who do care (for whom you are providing access) will still have a possibility to do so.
2009/1/10 Patrick Perry
: The reason I want to expose modules but hide the documentation is because there are a lot of "unsafeX" functions I want to provide access to, but which 99% of users don't care about. The array library does the same thing.
Patrick
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

Patrick Perry schrieb:
The reason I want to expose modules but hide the documentation is because there are a lot of "unsafeX" functions I want to provide access to, but which 99% of users don't care about. The array library does the same thing.
Alternatively, the DEPRECATED pragma may prevent programmers from using these functions too extensively. However, this may be considered abuse of this pragma. I think the Unsafe module is the cleanest solution.

On Sat, Jan 10, 2009 at 02:46:05AM -0800, Patrick Perry wrote:
Here's the haddock documentation; I'm not sure if Hackage honors {-# OPTIONS_HADDOCK hide #-} when it displays the exposed modules:
Who do you want the same modules to be both exposed and hidden?
participants (5)
-
David Waern
-
Eugene Kirpichov
-
Henning Thielemann
-
Patrick Perry
-
Ross Paterson