Changes between Version 34 and Version 35 of Commentary/Packages/GhcPackagesProposal


Ignore:
Timestamp:
Oct 5, 2006 8:29:56 AM (8 years ago)
Author:
simonpj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Commentary/Packages/GhcPackagesProposal

    v34 v35  
    3838 * Then, you can use the {{{-hide-package}}} flag to hide an otherwise-exposed package, and the {{{-package}}} flag to expose an otherwise-hidden package. 
    3939 
    40 When GHC incorporates package names in exported symbols, you will be able to expose package P1 when compiling module M (say), and expose P2 when compiling module N by manipulating these flags.  Then M and N could both import module A.B.C, which would come from P1 and P2 respectively. But: 
     40So, you can expose package P1 when compiling module M (say), and expose P2 when compiling module N by manipulating these flags.  Then M and N could both import module A.B.C, which would come from P1 and P2 respectively. But: 
    4141 * What if you wanted to import A.B.C from P1 and A.B.C from P2 into the ''same'' module? 
    4242 * What if you want to only replace ''parts'' of P1 (e.g., you want to use an updated version of a module in {{{base}}})?