Re: [Haskell-cafe] Unexported functions are evil

2005-05-16 Thread Samuel Bronson
On 15/05/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Taking this to an illogcial extreme, why don't we allow pointer arithmetic in Haskell, but require people to import Prelude.C first, so that people who enjoy playing with fire can do it? After all, we use it under the covers... Isn't

Re: [Haskell-cafe] Unexported functions are evil

2005-05-16 Thread Iavor Diatchki
Hello, On 15 May 2005 12:29:11 +0200, Peter Simons [EMAIL PROTECTED] wrote: ... On those occasions, however, why not put the function into a module, say Foo.Bar.Private and import it into Foo.Bar from there? Then those people who enjoy playing with fire _can_ use it, and everybody else will

Re: [Haskell-cafe] Unexported functions are evil

2005-05-15 Thread Ketil Malde
Peter Simons [EMAIL PROTECTED] writes: The only reason I could think of is that a function is considered to be internal, meaning: You don't want users of the module to rely on the function still being there (or still working the same way) in any of the next revisions. Right. (I guess you

Re: [Haskell-cafe] Unexported functions are evil

2005-05-15 Thread ajb
G'day all. Quoting Peter Simons [EMAIL PROTECTED]: I was wondering: Is there any reason why you would have a function in one of your modules and _not_ export it? The short answer: Because that function is nobody else's business. The long answer: The reason why programming is hard is that