Re: Test Cases for Configurations

2007-06-18 Thread Ian Lynagh
On Mon, Jun 18, 2007 at 01:51:06PM +0100, Simon Marlow wrote: > > > >It also means that none of your internal modules can depend on any of > >your normal modules. > > Sure they can - the foo-internal package would contain all the modules > (internal + external), but the foo package would only re-

Re: Test Cases for Configurations

2007-06-18 Thread Simon Marlow
Ian Lynagh wrote: On Mon, Jun 18, 2007 at 09:16:10AM +0100, Simon Marlow wrote: modules: ... modules[testing]: ... modules[internal]: ... A simpler way to solve this problem is to have two packages, with the first package (foo-internal) exporting all the modules, and the second (foo)

Re: Test Cases for Configurations

2007-06-18 Thread Ian Lynagh
On Mon, Jun 18, 2007 at 09:16:10AM +0100, Simon Marlow wrote: > > > >modules: ... > >modules[testing]: ... > >modules[internal]: ... > > A simpler way to solve this problem is to have two packages, with the first > package (foo-internal) exporting all the modules, and the second (foo)

Re: Test Cases for Configurations

2007-06-18 Thread Simon Marlow
Ian Lynagh wrote: On Fri, Jun 15, 2007 at 03:06:07PM +0200, Thomas Schilling wrote: On 15 jun 2007, at 14.09, Neil Mitchell wrote: this being common practice, and yet permit it occasionally. One thing I would like is given a package _data, which provides a data type, and a package _class whic