[Haskell-cafe] Hoogle and Network.Socket

Neil Mitchell ndmitchell at gmail.com
Fri Feb 20 04:17:46 EST 2009


> 1) Show all the functions (when the number is low), but place platform
> specific functions under separate headers: "Windows",
> "Linux/BSD/POSIX", "OS X", etc.

If a function isn't available on all OS's then all Hoogle would be
encouraging you to do is break compatibility and stop me from using
your software. If a function is only available on one OS you will
certainly have to deliberately choose to search for that, and it will
never show up by default.

For what shows up by default I more meant other packages. Should
Gtk2hs show up by default? What about tagsoup? What about base? Things
like Win32 will never show up by default.



> This way the users can remain as ignorant as I was and still find their data.
> 2) Detect the OS (when possible - perhaps difficult for the web/JS
> interface) and display the functions specific to the platform
> requesting the search.
> This has a small issue if you are searching on one platform and
> programming on/for another platform.  But the flags could still be
> used.
> Thomas
> On Thu, Feb 19, 2009 at 9:11 AM, Neil Mitchell <ndmitchell at gmail.com> wrote:
>> Hi
>> http://haskell.org/hoogle/?q=socket+%2Bnetwork
>> By default it searches the libraries supplied with Windows apart from
>> Network (for various technical reasons). If you add +network it will
>> then search the network library.
>> What libraries should Hoogle search by default? What flags should be
>> available to control which ones are searched? I have no idea, if you
>> do then say what you think and why!
>> Thanks
>> Neil
>> On Thu, Feb 19, 2009 at 2:50 AM, Thomas DuBuisson
>> <thomas.dubuisson at gmail.com> wrote:
>>> I recall that Niel made sure hoogle doesn't search through
>>> non-portable libraries (a shame), but I thought Network.Socket could
>>> be used on Windows and yet Hoogle does not give any results for
>>> 'socket' or any other functions within Network.Socket.
>>> First, am I mistaken and Network.Socket is POSIX only?  I could swear
>>> it wasn't.  Secondly - is there any chance of lifting the non-portable
>>> libraries ban, Niel?  From the stand point of an application developer
>>> it might not sound good, but even in Haskell some software is system
>>> level and bound to be single platform (case and point: XCB, xmonad,
>>> hsXenCtrl).  Judging by the amount of research in systems level
>>> functional programming I wouldn't be surprised to see this collection
>>> grow and making functions hard to find isn't productive.
>>> Thomas
>>> _______________________________________________
>>> Haskell-Cafe mailing list
>>> Haskell-Cafe at haskell.org
>>> http://www.haskell.org/mailman/listinfo/haskell-cafe

More information about the Haskell-Cafe mailing list