C#: Executing a Conditional With Object Initializer Syntax

Question

Suppose I have a simple class that Adds:

public class Multiply
{
     public int A {get; set;}
     public int B {get; set;}
     public int C {get; set;}

     public List<int> Result {get; set;}

     public void Calculate()
     {
         if (A != 0 && B!= 0 && C != 0)
         {
           Result.Add(A);
           Result.Add(B);
           Result.Add(C);
           Result.Add(A * B);
           Result.Add(A * C);
           Result.Add(B * C);
           Result.Add(A * B * C);
         }
     }
}

The above class models my actual application. I have a series of parameters that get set, in this case A, B and C. I then execute Calculate and use the Multiply object's Result property to access the result.

(There might be a better ways to accomplish this template; Lazy loading comes to mind. If you want to suggest a better template go for it but its not the purpose of my question; its just a simple example that illustrates my question.)

Here is my question:

If I'm using the Object Intializer Syntax:

Multiply m = new Multiplier()
{
   A = 1,
   B = 2,
   C = 3
}

m.Calculate();
DoSomething(m.Result[5]); //DoSomething(6);

Is there a way to execute Calculate() as part of the m initialization?

Josh · Accepted Answer · 2011-02-23 05:04:29Z

5

Make Result a read-only property and move the Calculate logic to it.

But no, you can't call methods with initializer syntax. Then it wouldn't be initializer syntax, it would just be some alternative C# syntax.

answered Feb 23, 2011 at 5:04

Josh

69.4k15 gold badges149 silver badges158 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Jim Schubert Over a year ago

I was about to post the same answer.

tangentstorm · Accepted Answer · 2011-02-23 05:08:29Z

1

Not as far as I know...

But: you could just do the calculation in the getter for Result.

Edit:

Since someone already posted that, you could also just force the arguments to go into your constructor instead of using the initialization block.

This is actually better since you're caching the result. The way your code works, you can change A,B, and C at any time, but the cached value doesn't change. By encapsulating those attributes and only putting them in the constructor, you prevent your object from falling into an inconsistent state, and you can put whatever code you want in the constructor.

answered Feb 23, 2011 at 5:08

tangentstorm

7,3752 gold badges33 silver badges39 bronze badges

1 Comment

mellamokb Over a year ago

And it took you 4 minutes to post that answer? At least check before writing a duplicate answer. That gets old fast.

Collectives™ on Stack Overflow

C#: Executing a Conditional With Object Initializer Syntax

2 Answers 2

1 Comment

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related