🚀 go-pugleaf

> But declaring public fields, not marked as const, should still be a real
> no-no.

Well, this whole thing has shore been a lesson to me!

Many thanks to all who responded.  This is why the Borland (Devco?) 
community is so great!

Best regards,
Dr. Bob Miller


"Joanna Carter [TeamB]" <joanna@not.for.spam> wrote in message 
news:44f555aa@newsgroups.borland.com...
> "Marc Rohloff [TeamB]" <"on request"> a �crit dans le message de news:
> 1j04hi3wixlhw.dlg@dlg.marcrohloff.com...
>
> |   class MyClass
> |   {
> |      public int x;
> |      public static readonly int c2 = 5;
> |   }
> |
> |   public static void Main()
> |   {
> |      Console.WriteLine("c1 = {0}, c2 = {1}", MyClass.c1, MyClass.c2
> | Console.WriteLine("c1*4 = {0}, c2*4 = {1}", MyClass.c1*4, MyClass.c2*4
> | );
> |
> | In the second WriteLine the compiler will pre calculate the value 20,
> | for c2 it will perform the calculation on each execution.
> |
> | A couple of points 'const' fields are automatically static and
> | read-only.
>
>
> Yes, I had forgotten that they were static, even if not declared as such.
> But declaring public fields, not marked as const, should still be a real
> no-no. Bob's suggestion of read-only properties is a valid solution, for
> those who don't mind typing :-)
>
> Joanna
>
> -- 
> Joanna Carter [TeamB]
> Consultant Software Engineer
>
>