caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Chris Hecker <checker@d6.com>
To: "M E Leypold @ labnet" <leypold@informatik.uni-tuebingen.de>
Cc: tom.hirschowitz@inria.fr, caml-list@inria.fr
Subject: Re: [Caml-list] mixin modules paper and future?
Date: Thu, 29 Aug 2002 19:21:42 -0700	[thread overview]
Message-ID: <4.3.2.7.2.20020829191906.02985970@mail.d6.com> (raw)
In-Reply-To: <15725.62310.16647.701975@hod.void.org>


> > I think that this is an incredibly important feature for
> > caml to make headway into large systems development.
>Do you think so?

You misunderstood what I thought was important, or I was unclear, or 
both.  ;)  I think shipping the mixin system (or any system that allows 
module recursion) is important, not the open problems themselves.  All of 
the examples you mentioned (well, I don't know about Cobol, but all the 
others) allow you to have recursive systems spread across multiple files to 
reduce compile times, limit file length, and break things out conceptually.

The concept of a "forward declaration" is critical to writing large scale 
software effectively, I think.

Chris


-------------------
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


      parent reply	other threads:[~2002-08-30  2:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27  3:33 Chris Hecker
2002-08-28  8:43 ` Tom Hirschowitz
2002-08-28 19:25   ` Chris Hecker
2002-08-29 10:11     ` M E Leypold @ labnet
2002-08-29 18:47       ` [Caml-list] objective caml and industry james woodyatt
2002-08-29 22:57         ` Michael Vanier
2002-08-29 23:52           ` james woodyatt
2002-08-30 13:13           ` Vitaly Lugovsky
2002-08-30 23:23             ` Michael Vanier
2002-08-30  2:25         ` Chris Hecker
2002-08-30 18:14           ` Jonathan Coupe
2002-09-01  9:18             ` What kind of industry do you mean? (Was: [Caml-list] objective caml and industry) Mattias Waldau
2002-09-01 20:15               ` Markus Mottl
2002-09-01 21:10                 ` [Caml-list] wxOCaml? Dave Mason
2002-09-02  6:23                 ` [Caml-list] Re: What kind of industry do you mean? (Was: objective caml and industry) Michaël Grünewald
2002-09-02 12:43               ` What kind of industry do you mean? (Was: [Caml-list] " Alessandro Baretta
2002-09-02 22:58                 ` Gerd Stolpmann
2002-09-03  6:58                   ` [Caml-list] Re: An XML standard API? (was:What kind of industry do you mean?) Alessandro Baretta
2002-09-02 18:15               ` What kind of industry do you mean? (Was: [Caml-list] objective caml and industry) Oleg
2002-08-30 18:14           ` [Caml-list] objective caml and industry Jonathan Coupe
2002-08-31  2:26         ` John Max Skaller
2002-09-02 18:38           ` Oleg
2002-08-30  2:21       ` Chris Hecker [this message]

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=4.3.2.7.2.20020829191906.02985970@mail.d6.com \
    --to=checker@d6.com \
    --cc=caml-list@inria.fr \
    --cc=leypold@informatik.uni-tuebingen.de \
    --cc=tom.hirschowitz@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).