| Haskell 98: A non-strict, purely functional language. Technical report, The Haskell 98 Committee, 1 Feb. 1999. Currently available at http://haskell.org. |
....for Y. There is a single global namespace for component names. Mutual dependencies between modules is possible, but there is no mechanism for black box reuse of modules and no support for hierarchical structuring of modules within modules. Languages like Ada [9] Modula 3 [25] and Haskell [1] support a kind of module which we will call packages. With packages, there is a flat namespace of modules; by convention module names correspond to filenames. Connections are hard wired to module names: If module X uses module Y, then any replacement for Y must also be named Y and support at ....
Haskell 98: A non-strict, purely functional language. Technical report, The Haskell 98 Committee, 1 Feb. 1999. Currently available at http://haskell.org.
....for Y. There is a single global namespace for component names. Mutual dependencies between modules is possible, but there is no mechanism for black box reuse of modules and no support for hierarchical structuring of modules within modules. Languages like Ada [Bar96] Modula 3 [Har91] and Haskell [Jon99] support a kind of module which we will call packages. With packages, there is a flat namespace of modules; by convention module names correspond to filenames. Connections are hard wired to module names: If module X uses module Y, then any replacement for Y must also be named Y and support at ....
Haskell 98: A non-strict, purely functional language. Technical report, The Haskell 98 Committee, 1 February 1999. Currently available at http://haskell.org.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC