[Mono-list] RE: forgive me & taking ownership
17 Jul 2001 12:05:21 -0400
So far we've been doing 1 file per class/enum, and I personally like it
that way. Same thing for interfaces. I think it makes maintaining the
code easier, especially in distributed projects with lots of
contributers (thanks everyone!)
On 17 Jul 2001 12:05:31 -0400, Michael Lambert wrote:
> > From: Garrett Rooney <firstname.lastname@example.org>
> > Subject: Re: [Mono-list] forgive me
> > On Mon, Jul 16, 2001 at 04:09:25PM -0500, Reggie Burnett wrote:
> > > Forgive me if I missed this on the site, but how does someone go about
> > > setting up an environment where they can work on classes or such? What
> > > tools should I use?
> > >
> Suggest, cygwin32 and gvim
> > I'm just using the Microsoft Beta-2 .Net SDK. It'll complain that your class
> > is overriding one in the standard library, but you can solve that by either
> > using a different namespace while you develop, or passing /nowarn:1595 on the
> > command line for csc.exe.
> I just rename my classes Zfoo instead of foo when checking.
> I don't think anyone has picked up the following enums and I would like to
> write them up. Get them all done at once kind of thing. Asking this is
> probably a mistake but... Does any have a preference whether: each assembly
> namespace (ex: corlib/System) has a file called enums.cs or one file per enum
> (corlib/System/AttributeTargets.cs)? These are from the standard so it is
> unlikely that they will change. I've worked on project that go either way but
> prefer the one file per class (as it allows you to easily locate the file in the
> source tree) most of the time except in cases like this.
> Michael Lambert
> Mono-list maillist - Monoemail@example.com