From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24816 invoked by alias); 1 Dec 2002 17:55:04 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 24783 invoked from network); 1 Dec 2002 17:55:03 -0000 Received: from unknown (HELO ops2.one-point.com) (216.234.116.146) by sources.redhat.com with SMTP; 1 Dec 2002 17:55:03 -0000 Received: from localhost (jsturm@localhost) by ops2.one-point.com (8.11.6/8.11.6) with ESMTP id gB1Ht4B13955; Sun, 1 Dec 2002 12:55:04 -0500 Date: Sun, 01 Dec 2002 09:55:00 -0000 From: Jeff Sturm To: Anthony Green cc: java-patches@gcc.gnu.org, Subject: Re: Java Patches: -fno-org-xml-sax and -fno-org-w3c-dom In-Reply-To: <1038718968.31616.23.camel@escape> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-12/txt/msg00020.txt.bz2 On 30 Nov 2002, Anthony Green wrote: > We recently discussed moving org.xml.sax and org.w3c.dom into their own > shared libraries, and adding a compiler flag to turn off linking them in > by default. After some reflection it seems like a single flag isn't > really a good idea. The -fno-jaxp idea isn't really workable as jaxp > will change over time. The scheme implemented below seems flexible > enough... What would be the harm in _not_ linking these libraries by default? With this patch, I either have to alter all my makefiles, or accept that each binary I link requires two new DSOs. Alternatively, if -l-org-xml-sax and -l-org-w3c-dom aren't linked automatically, existing binaries are unaffected and no front-end changes are required. Those who need the libraries can just add the linker flags (or use xerces). In any case I think breaking org.xml and org.w3c out of libgcj.so is a great idea. > + org/xml/sax/helpers/NewInstance.java \ BTW this class doesn't appear to be in the tree. Jeff