caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Mattias Waldau" <mattias.waldau@abc.se>
To: "Charles Martin" <martin@chasm.org>, <caml-list@inria.fr>
Subject: RE: Module hierarchies
Date: Sun, 7 Jan 2001 11:10:17 +0100	[thread overview]
Message-ID: <HDEEKOMJILGEIHIMAPCDKECADNAA.mattias.waldau@abc.se> (raw)
In-Reply-To: <5.0.0.25.0.20010106112842.00a3eeb0@chasm.org>

Interesting idea, and if it can be done without any penalty for people
who doesn't need it, it would be a nice addition to Ocaml.


Java and overview
=================

Java programming with a lot of files in a lot of different directories isn't
very nice. It is very difficult to get a good overview of the part of the
project you are improving.

However, in Java there are three things that destroys overview, and
I don't know which one is worst

1. size of code, java programs are long, and there is a lot of nonsense
   rows (for example accessors)
2. one class per file (true for 95% of the classes)
3. spreading the program over many different directories.

In order to solve this, a lot of graphical tools are built and sold to help
people get the overview, like class browsers, UML....


/mattias

P.s Note that nonsense rows is also true for some part of Ocaml, for
that I have to write accessors for objects attributes.



  reply	other threads:[~2001-01-07 20:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-06 19:32 Charles Martin
2001-01-07 10:10 ` Mattias Waldau [this message]
2001-01-07 16:07 ` Michael Hicks
2001-01-09  8:03   ` John Max Skaller
2001-01-07 20:37 ` Vitaly Lugovsky
2001-01-08 10:24 ` Xavier Leroy
2001-01-08 14:01   ` Judicael Courant
2001-01-09 16:46 Dave Berry
2001-01-10  9:40 ` Markus Mottl
2001-01-09 17:34 Daniel Ortmann
2001-01-09 18:06 Dave Berry
2001-01-10 20:12 ` Gerd Stolpmann
2001-01-11 12:53 Dave Berry

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=HDEEKOMJILGEIHIMAPCDKECADNAA.mattias.waldau@abc.se \
    --to=mattias.waldau@abc.se \
    --cc=caml-list@inria.fr \
    --cc=martin@chasm.org \
    /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).