From: Dalibor Topic <robilad@kaffe.org>
To: Martin Olsson <mnemo@minimum.se>
Cc: audriusa@bluewin.ch, mauve-discuss@sources.redhat.com
Subject: Re: Mauve coding on Windows
Date: Sat, 10 Sep 2005 14:49:00 -0000 [thread overview]
Message-ID: <4322F252.7080604@kaffe.org> (raw)
In-Reply-To: <4323313D.7090205@minimum.se>
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
next prev parent reply other threads:[~2005-09-10 14:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 18:58 Martin Olsson
2005-09-09 20:01 ` Meskauskas Audrius
2005-09-09 23:54 ` Martin Olsson
2005-09-10 7:35 ` Meskauskas Audrius
2005-09-10 7:59 ` David Gilbert
2005-09-10 9:30 ` Mauve coding on Windows: The majority of tests runs under Windows Meskauskas Audrius
2005-09-10 10:18 ` Mauve coding on Windows Martin Olsson
2005-09-10 14:49 ` Dalibor Topic [this message]
2005-09-10 6:47 ` David Gilbert
2005-09-10 8:58 ` Andrew Haley
2005-09-10 17:15 ` Meskauskas Audrius
2005-09-16 17:08 ` Tom Tromey
2005-09-16 18:12 ` Meskauskas Audrius
2005-09-10 10:28 Jeroen Frijters
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=4322F252.7080604@kaffe.org \
--to=robilad@kaffe.org \
--cc=audriusa@bluewin.ch \
--cc=mauve-discuss@sources.redhat.com \
--cc=mnemo@minimum.se \
/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).