Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!uw-beaver!zephyr.ens.tek.com!tektronix!percy!m2xenix!news
From: news@m2xenix.psg.com (Randy Bush)
Newsgroups: comp.lang.modula2
Subject: Re: definition module loops
Message-ID: <1991May18.023154.1971@m2xenix.psg.com>
Date: 18 May 91 02:31:54 GMT
References: <9105161749.AA06495@ctc.contel.com> <1991May17.162223.5539@iitmax.iit.edu>
Organization: Pacific Systems Group, Portland Oregon US
Lines: 12

gkt@iitmax.iit.edu (George Thiruvathukal) writes:

> I would suggest that what ought to be disallowed are cycles which arise in
> the "import" graphs (whose nodes are both definition and implementation
> modules) and edges are "imports."  Thus, two different modules
> (implementation parts) can borrow definitions and procedures from each other.

Watch out.  Their initialization bodies should not depend on [ procedures which
use or ] values provided by the other.  This is non-trivial to detect, even
without worrying about type transfer and other sinful acts.
-- 
Randy Bush  / news@psg.com  / ..!uunet!m2xenix!news