[Mono-dev] the c# compiler code

Kornél P?l kornelpal at hotmail.com
Fri Aug 26 14:18:58 EDT 2005

The following does not specific to mcs code it's my opinion about splitting

I think having a clean and well organized source code is required for
efficient development.

When splitting is done by copying files using SVN then removing unnecessary
parts from each file SVN history will remain. Then as a different revision
modifications can be made to the files. This way modifications can be

Don't you think this solution is acceptable?


----- Original Message -----
From: "Miguel de Icaza" <miguel at ximian.com>
To: "Eduard Ralph" <mono at eduard-ralph.de>
Cc: <mono-devel-list at lists.ximian.com>
Sent: Sunday, August 21, 2005 7:33 PM
Subject: Re: [Mono-dev] the c# compiler code


> I’m currently working on expanding the c# compiler for my personal
> syntax. (the /mcs code, not gmcs). As part of that I noticed that the
> compiler code is a bit messy and not well documented. I would touch up
> the code I run into while working on my own expansion. That would
> require creating new files to split some of the classes out of the C#
> files and renaming a few of them aside from restructuring the Methods
> and renaming some of them.
> Is there any point in spending time on that and is there interest in
> that?

We have no interest in integrating such changes into mcs.

The reason is not that I dislike the idea of splitting it up, but the
fact than the repository "history" would be rendered useless.

The history is a very important tool that we use to keep track of
changes, rationale, groupped commits and so on and it matters more to us
than the actual physical organization.

Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com

More information about the Mono-devel-list mailing list