Well I agree it's not ideal. But from what you say it's working as advertised. It's not easy to derive hs-boot from hs, because you probably don't want to put all the type sigs in the hs file into the hs-boot file, because that might create yet more dependencies for the hs-boot file. Also a common thing is to put a data type decl into the hs-boot file without constructors, and there's not automatic way to decide whether to do that. Simon | -----Original Message----- | From: glasgow-haskell-users-bounces@haskell.org [mailto:glasgow-haskell-users-bounces@haskell.org] | On Behalf Of Serge D. Mechveliani | Sent: 12 August 2006 16:25 | To: glasgow-haskell-users@haskell.org | Subject: recursive import | | Please, discard my previous request for the help with .hs-boot. | | I seem to get through the .hs-boot matter. | We shall see further. | | Still it looks strange. | The compiler reports errors: this and this thing must not be in | .hs-boot. | As it understands everything, it could take the .hs copy and filter | what is needed for .hs-boot. | Why the user needs to create .hs-boot by hand? | | ----------------- | Serge Mechveliani | mechvel@botik.ru | | _______________________________________________ | Glasgow-haskell-users mailing list | Glasgow-haskell-users@haskell.org | http://www.haskell.org/mailman/listinfo/glasgow-haskell-users