public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "m4341 at abc dot se" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/24832] Modularization of Java libraries
Date: Mon, 14 Nov 2005 19:18:00 -0000	[thread overview]
Message-ID: <20051114191834.8243.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24832-7817@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from m4341 at abc dot se  2005-11-14 19:18 -------
Created an attachment (id=10237)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10237&action=view)
Proposal for the initial split.

This is the initial split I did, and I must admit that it isn't thoroughly
tested.
There are one text file for each module I created. The text file contains an
initial dependency description and a list of files incorporated in that module.

In addition to this there is one Java-file with code modified to dynamically
load the DefaultContentHandlerFactory that now resides in the AWT package from
the URLConnection class. This wasn't necessary earlier. Beware that this is
completely untested and I see it as a proposed modification.

I REALLY wanted to break out the security classes too, since they have a
significant size and aren't really needed on an embedded system. This is my
minimal effort breakup - it could have been even better.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24832


      parent reply	other threads:[~2005-11-14 19:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-13 10:54 [Bug libgcj/24832] New: " m4341 at abc dot se
2005-11-14 13:17 ` [Bug libgcj/24832] " pinskia at gcc dot gnu dot org
2005-11-14 13:17 ` pinskia at gcc dot gnu dot org
2005-11-14 19:18 ` m4341 at abc dot se [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=20051114191834.8243.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).