From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28376 invoked by alias); 28 Nov 2007 12:39:49 -0000 Received: (qmail 28367 invoked by uid 22791); 28 Nov 2007 12:39:48 -0000 X-Spam-Check-By: sourceware.org Received: from ms9.webland.ch (HELO ms9.webland.ch) (194.209.78.139) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 28 Nov 2007 12:39:42 +0000 Received: from indel.ch ([84.73.11.188]) by ms9.webland.ch (Webland.MailServer.v.8.9.6) with ASMTP id HXP63738 for ; Wed, 28 Nov 2007 13:39:38 +0100 Received: from FABI.indel.ch [192.168.1.91] by indel.ch [127.0.0.1] with SMTP (MDaemon.v2.7.SP5.R) for ; Wed, 28 Nov 2007 13:30:56 +0100 Message-Id: <5.2.0.9.1.20071128133240.01d41350@localhost> X-Sender: cenedese@localhost X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 [via SMTPAuth 0.9, bisswanger.com] Date: Wed, 28 Nov 2007 12:49:00 -0000 To: gcc-help@gcc.gnu.org From: Fabian Cenedese Subject: Re: reduce compilation times? In-Reply-To: <474D5CC1.9050008@ellipticsemi.com> References: <998d0e4a0711280400o573020fek29ce1661f3dec823@mail.gmail.com> <18597F2B47F1394A9B309945EC72411201344B58@servex01.wamas.com> <998d0e4a0711280400o573020fek29ce1661f3dec823@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MDaemon-Deliver-To: gcc-help@gcc.gnu.org X-Return-Path: cenedese@indel.ch X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2007-11/txt/msg00354.txt.bz2 >>Splitting C files is different to splitting C++ files or splitting Java files, >>Fortran, Ada, ObjC, .... > >In the case of C++, you can just put each method of a class in a separate .C file. Provided they all include a .H file which defines the class prototype it's ok. The problem may not be the .cpp but the .h files. If I add a new member or method all files of this class need to be rebuilt. With the independent functions in C this may be easier to do. But still, if everything is rebuilt then it doesn't matter how many files you spread your code over. Of course from maintenance point of view splitting files is good though I maybe wouldn't go down to function level, more like class level. Otherwise the bad overview in the file is just transferred to the project level. bye Fabi