From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3052 invoked by alias); 10 Sep 2005 14:49:19 -0000 Mailing-List: contact mauve-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sources.redhat.com Received: (qmail 3031 invoked by uid 22791); 10 Sep 2005 14:49:15 -0000 Received: from p54a54f50.dip.t-dialin.net (HELO clerks.kaffe.org) (84.165.79.80) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 10 Sep 2005 14:49:15 +0000 Received: from [127.0.0.1] (clerks.kaffe.org [127.0.0.1]) by clerks.kaffe.org (8.13.4/8.13.4) with ESMTP id j8AEn156016092; Sat, 10 Sep 2005 16:49:04 +0200 Message-ID: <4322F252.7080604@kaffe.org> Date: Sat, 10 Sep 2005 14:49:00 -0000 From: Dalibor Topic User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc4 (X11/20050720) MIME-Version: 1.0 To: Martin Olsson CC: audriusa@bluewin.ch, mauve-discuss@sources.redhat.com Subject: Re: Mauve coding on Windows References: <432259B7.70208@minimum.se> <4321E9E6.1020308@bluewin.ch> <43229EF9.5090408@minimum.se> <43228CB8.2060305@bluewin.ch> <4323313D.7090205@minimum.se> In-Reply-To: <4323313D.7090205@minimum.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-q3/txt/msg00030.txt.bz2 Martin Olsson wrote: > When and if someone fixes the naming problems you got atleast one more > developer going into the project; me. Good, let's do it. > If my Eclipse error log is complete it's a matter of renaming at a very > minimum say 25 files (or the corresponding dirs ofc). But it would be > much nicer to have a consistant naming for the entire directory > structure. I would definately vote for renaming the classes that test > class Xxxx to XxxxClass instead of Xxxx_ because I think the first name > is more descriptive and would confuse mauve newcomers less. I'd say, go with XxxClass to rename the classes, rather than packages/directories. Can you send in a patch? As for consistency, I guess one could spend a lot of time arguing for the most consistent naming of all the test cases, but ... let's just leave it as it as long as no pressing reason comes up, and do the minimally invasive thing. When someone wants to check out mauve on a DOS FAT file system, we can worry about the 8+3 naming limitations then, for example. cheers, dalibor topic