Hello, > > As an example, the generics compiler has been developed on a separate > > directory for almost a year, and we have to integrate patches every day. > > The anonymous method code lived only on my hard drive as a copy of the > > repository for six months, and I had to go through the same problems. > > Ok. But integrating that is a pain (I assume that's manual). Well, > if it's the same case at many places, I would also live with it... :-(
Actually, it is rather simple if you happen to keep your code under revision control instead of making a full fork. By keeping it under revision control, you can `svn update' and you will get a couple of conflicts every once in a while. It is not like the parser changes a lot, so most of the time it will be easy. If you are having problems merging the code I can assure you that it is because you are not using cvs/svn to assist you. > > I do not like the idea of checking work-in-progress code to the > > compiler, because that code tends to be bit rot if the work is not > > completed. > > Ok. Agree... > > Hooh! Going by the examples of "generics" and "anonymous methods", > I'd let mcsdoc evolve separately and once done report back with final > code. Excellent. Miguel. _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
