Re: Portability dreams

1999-06-23 Thread Hannah Schroeter
On Fri, May 28, 1999 at 04:18:57AM -0700, Simon Marlow wrote: [...] * Make compilation of simple programs a simple thing for Joe User. We could include ghcmake with ghc - then it's just a case of typing 'ghcmake' in a directory that contains at least Main.hs. I've got hmake to run with

RE: Portability dreams

1999-05-28 Thread Simon Peyton-Jones
[...] What you're really saying is: "if the libraries that you compiled your program against change, you have to recompile your program." Not doing this is dodgy at best, even for C. Sven Panne: Huh? Doing this perfectly fine, see Giuliano's mail. Let me elaborate: you can't link

RE: Portability dreams

1999-05-28 Thread Simon Marlow
[ moved to glasgow-haskell-users from haskell ... ] Simon Marlow: [...] What you're really saying is: "if the libraries that you compiled your program against change, you have to recompile your program." Not doing this is dodgy at best, even for C. Sven Panne: Huh? Doing this perfectly

Re: Portability dreams

1999-05-28 Thread Kevin Atkinson
Sven Panne wrote: * If you upgrade your version of GHC, its libraries change in such a way that you have to recompile all your code: A compiler-generated entity (ds42, lvl1, tpl60, ...) from one version can mean quite a different thing in the next. Compare this with C

Re: Portability dreams

1999-05-28 Thread Giuliano Procida
On Thu, May 27, 1999 at 03:51:57PM +0200, Sven Panne wrote: Using Haskell programs and libraries with different compilers and/or interpreters (or even with different versions of the same system!) is currently quite a frustrating experience. This is can be attributed to the following problems:

Re: Portability dreams

1999-05-28 Thread Sven Panne
Simon Marlow wrote: [...] We (GHC) are compatible with hbc in this area I think - hbc defines __HASKELL1__=3 for Haskell 1.3, we define __HASKELL1__=5 and __HASKELL98__. Hmmm, I must have missed the equation Haskell 1.5 = Haskell 98 somehow...:-) [...] I don't see a problem with

Re: Portability dreams

1999-05-28 Thread Malcolm Wallace
Sven Panne writes: Using Haskell programs and libraries with different compilers and/or interpreters (or even with different versions of the same system!) is currently quite a frustrating experience. I agree. And as the current maintainer of one of the Haskell systems, I'd like to work both

Re: Portability dreams

1999-05-28 Thread Sven Panne
\begin{sarcasm} Malcolm Wallace wrote: [...] all 1.3/1.4 code should be converted or thrown away. HaXml? ;-)) [...] so one compiler writer has no idea what another compiler writer is using, "man grep" :-) [...] For another, you have chosen to use deliberately preprocessor directives.

Re: Portability dreams

1999-05-28 Thread Sven Panne
Kevin Atkinson wrote: [...] C++ stores type information in the symbol to resolve overloading. Ghc might do a similar thing. Than again Haskell overloading is nothing like C++ overloading so maybe not. There's nothing wrong with this kind of name mangling: When the library is updated, the

Portability dreams

1999-05-27 Thread Sven Panne
Using Haskell programs and libraries with different compilers and/or interpreters (or even with different versions of the same system!) is currently quite a frustrating experience. This is can be attributed to the following problems: * Different language versions (1.3, 1.4, 98, ...) exist.