Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Fri, 24 May 2002 20:45:26 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: splitting dependencies in cygwin1.dll Message-ID: <20020525004526.GA19249@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Fri, May 24, 2002 at 07:37:31PM +1000, Robert Collins wrote: >I'd like to split out some of the classes & headers in cygwin1.dll to >make it more loosely coupled. This wouldn't make it less able to use >inlined calls, but would reduce recompiles where non-related things >have not actually changed. > >I'd also like to make the headers consistently forward declare required >classes / include their own pre-requisite headers (with forward >declarations preferred). > >I'll run all such changes through cygwin-patches for review, but first: >do you have any objections to this being done? Perhaps you may recall a similar request a few months ago, where someone was going to "fix" the cygwin headers. At that time, I said that I didn't want to get into a discussion of the best way to deal with headers and I mentioned that I wasn't going to have headers include other headers at that time. That hasn't changed. Robert, if you're looking for things to do, why not finish the sysv ipc cygserver work? I think that would be much more bang for the buck than messing with headers. cgf