This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RFC: Moving C to its own directory
- From: Andreas Jaeger <aj at suse dot de>
- To: Neil Booth <neil at daikokuya dot co dot uk>
- Cc: gcc at gcc dot gnu dot org
- Date: Sun, 01 Jun 2003 22:03:46 +0200
- Subject: Re: RFC: Moving C to its own directory
- References: <20030601191930.GC5311@daikokuya.co.uk>
Neil Booth <neil@daikokuya.co.uk> writes:
> Following a brief discussion with rth at the summit, and just
> now on IRC, I thought I'd post what the current plan is.
>
> 1) Create a directory fe/
> 2) Create a directory fe/c/
> 3) Move c-specific and C common files, like c-lex.c, there.
> 4) Move objc/ to fe/ too.
>
> I originally suggested fe/c/c/ fe/c/cp/ and fe/c/objc, but Zack
> thought that was overkill and made configury harder, though I
> still like the separation myself.
>
> cp/, f/ and java/ and (ugh) ada/ should be moved too, but I'm not
> volounteering to do those.
Separating the files so that we have for each "module" or logical unit
a separate directory, sounds fine!
Will this also result in a backend directory?
> If there are no further comments, I will do 1-4) some time in the
> future. I'm quite busy at present, so it'll probably be at least
> 2 months.
The problem that I see is that moving files around, we lose the CVS
history. We could still get to the old versions but cannot do a real
"cvs annotate". So, I suggest to do the move in the repository and
copy the complete files around.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj