From: "Christopher A. Watford" <christopher.watford@gmail.com>
To: brogoff <brogoff@speakeasy.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Circular module dependencies
Date: Tue, 7 Sep 2004 09:39:29 -0400 [thread overview]
Message-ID: <8008871f040907063960835f65@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409070524360.32038@shell2.speakeasy.net>
On Tue, 7 Sep 2004 05:36:18 -0700 (PDT), brogoff <brogoff@speakeasy.net> wrote:
>>>SNIP>>>
> In general, I agree that this can be a design error, but refactorings that
> are reasonable for toy code posted during an internet email discussion may not
> make sense when we're talking about files that are tens of thousands of lines
> long even in very high level languages. Scale changes everything.
>
> -- Brian
I run across this problem all the time at work with C/C++ header
files. The difference here is C/C++ allows forward declarations which
remove the need for cyclic includes. However, it adds on maintenance
requirements for renaming structures and classes and their
declarations all over the place if things get messy.
I'm glad OCaml atleast 'seems' to have a more well defined approach to
cyclic dependencies.
--
Christopher A. Watford
christopher.watford@gmail.com
http://dorm.tunkeymicket.com
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-09-07 13:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 9:17 Tony Edgin
2004-09-07 2:28 ` Jacques GARRIGUE
2004-09-07 17:10 ` Christopher Dutchyn
2004-09-07 4:39 ` brogoff
2004-09-07 6:12 ` Erik de Castro Lopo
2004-09-07 12:36 ` brogoff
2004-09-07 13:39 ` Christopher A. Watford [this message]
2004-09-08 0:30 ` Erik de Castro Lopo
2004-09-07 6:14 ` Nicolas Cannasse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8008871f040907063960835f65@mail.gmail.com \
--to=christopher.watford@gmail.com \
--cc=brogoff@speakeasy.net \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).