On Fri, 2005-07-29 at 00:07 +0200, Andreas Nahr wrote:
> No Consts.cs aren't automatically generated.
> The problem is, that several Attributes of classes in System.Web do not use
> the consts scheme, and about one third of your (BIG) patch is just for
> changing these Attributes.
> We will then have to change these again later, so it might make sense do do
> it now instead of doing it twice (and adding lots of changelog entries
> twice).
If we really want to be clever, and avoid doing things twice, we can put
this:
internal class MonoConsts {
#if ...
public string FXVersion = ...
#elif ...
...
#endif
}
in the common build directory. This way, the next time we need to target
another FX, we don't have to do it in 100 places.
The Const.cs is probably still a good idea, since it is really ugly to
have those magic names lying around the source code.
-- Ben
_______________________________________________
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
