recursive import

[Serge D. Mechveliani]

Concering the current state of recursive import,
Simon Peyton-Jones <simonpj at microsoft.com> writes on 5 Jun 2006

> [..]
>
> GHC's module-at-a-time compilation model means that GHC needs an hs-boot
> file to "get started".  The manual tries to explain what you can and
> can't do.  If you follow the rules it works pretty well.  We use
> recursive modules extensively for compiling GHC itself, and it's just
> fine with 'make'.  (ghc -M does the right thing.)
>
> [..]


Thank you for the explanation.

And how does this feature interact with packages, with making via 
Cabal ? Will Cabal work with recursive imports and with

  ghc-options:
    -fglasgow-exts -fallow-undecidable-instances
    -fallow-overlapping-instances -fno-warn-overlapping-patterns
    -fwarn-unused-binds -fwarn-unused-matches -fwarn-unused-imports
    -O 
    -prof -auto-all
?

Generally, I tend to use recursive modules because they simplify 
the global algorithm presentation. But fear of technical 
difficulties in the project support. Maybe, I would try this 
recursion.

-----------------
Serge Mechveliani
mechvel at botik.ru