Hi Michael, It would be interesting to hear about the situation that led to a cyclic dependency.
The few cases where I have had a problem I managed to solve it by moving all structure definitions into a separate module structs.rkt and then requiring that module everywhere else. /Jens Axel 2015-05-25 11:52 GMT+02:00 Michael Tiedtke <michael.tied...@o2online.de>: > As I had to find out Racket's module system doesn't support cyclic > dependencies. In that case I should use units. But as far as I have > understood the concept of full fledged units I must either write a lot of > redundant code like *signature auto^*, *implementation auto@,* *import > auto^*, *require "auto.rkt",* *export auto^* etc > OR I could create a lot of files following a certain naming conventions > when using whole module units. Both approaches are more hassle than > managing the respective files of my "framework" with copy&paste and via > *include.* > > *Isn't there any simple way to declare cyclic dependencies?* > > Can I put the signature and the implementation into one file? > > How do I require or import such an interdependent unit framework? Do I > have to use invoke-unit or require or ...? > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- Jens Axel Søgaard -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
