[Mono-list] RE: forgive me & taking ownership

[Miguel de Icaza]

> 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.

What if we group enumerations by "topic", like:

FileEnums.cs
	FileAccess
	FileMode
	FileShare

SocketEnums.cs:
	SocketFlags
	SocketOptionLevel
	SocketOptionName
	SocketShutdown
	SocketType
	
Ie, just a bit more descriptive than `enums.cs'.  And I agree, we
probably do not want a file per enum.

I would say that I would be glad to make an exception and move enums
into existing classes if they are only used by a single class.