Re: [Mono-dev] DateTime/DateTimeFormatInfo patch to reduce Clone()

2006-12-06 Thread Jonathan Pryor
On Wed, 2006-12-06 at 14:34 +0900, Atsushi Eno wrote: Mirco Bauer wrote: *cough* lack of const *cough* I quite don't understand it - unless you think you can declare const arrays (which is incorrect). He's saying that the Common Language Specification should have had the concept of C++

Re: [Mono-dev] DateTime/DateTimeFormatInfo patch to reduce Clone()

2006-12-05 Thread Atsushi Eno
Mirco Bauer wrote: On Mon, 2006-12-04 at 20:09 +0100, Paolo Molaro wrote: On 11/30/06 Atsushi Eno wrote: I noticed that many string[] properties in DateTimeFormatInfo are used directly in DateTime. They have to return Clone() which are not neccessary there. If the arrays are exposed to the

Re: [Mono-dev] DateTime/DateTimeFormatInfo patch to reduce Clone()

2006-12-04 Thread Paolo Molaro
On 11/30/06 Atsushi Eno wrote: I noticed that many string[] properties in DateTimeFormatInfo are used directly in DateTime. They have to return Clone() which are not neccessary there. If the arrays are exposed to the user, we should clone them, otherwise the user can change the values in the

[Mono-dev] DateTime/DateTimeFormatInfo patch to reduce Clone()

2006-11-30 Thread Atsushi Eno
Hello, I noticed that many string[] properties in DateTimeFormatInfo are used directly in DateTime. They have to return Clone() which are not neccessary there. using System; using System.Globalization; class Test { public static void Main () { for (int i