another preference question....

[Dario Solera]

Leslie Sanford wrote:

Instead, I must remember to call Dispose where it is implemented.

Not really needed if the object does not consumes lots of memory... Dispose/Finalize is invoked automatically (but not necessarily immediately) when the instance goes out of scope.

If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Blog - My Photos - ScrewTurn Wiki

[Leslie Sanford]

Joergen Sigvardsson wrote:

IMO, it boils down to this: 1) If the object is a first class entity - i.e., not a handle - then do initialization and finalization in constructor and destructor 2) If the object is a simple handle (such as a CWnd derivative), then there are two life lines - the handle object itself and whatever it's handling. Then I use init()/cleanup() to handle the life line of the handled object. My reason for 2) is that the destruction of handled object may fail - something I don't want to deal with in a destructor (if you say exception, then you've not only shot yourself in the foot, but you've also blown your brains out). Also, I might want to be able to share the handled object between handles, or I might just want to transfer the responsibility of it elsewhere. Note that this isn't something I've learned in school. I've picked it up as I go...

Hmm, interesting viewpoint. As someone who's written a lot of "wrapper" classes, I find your approach interesting. I'll have to give it some thought.

[pbraun]

Patrick Sears wrote:

call them inside the constructor

There are very valid reasons to use them outside of the constructor as well. When one is developing the class, one needs to be clear as to the reasons why the constructor and destructors are separate.

Phil

[El Corazon]

Nemanja Trifunovic wrote:

and was widely used before exceptions were available for C++.

the advantage of me learning from books later in the game. :laugh: Actually, that explains a lot. Thanks.

_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)

[Member 96]

I'm with you on this one, I really can't see the need for all those extra methods, it seems error prone and messy to me. Of course I didn't learn how to program in an ivory tower either. ;)

---

"I don't want more choice. I just want better things!" - Edina Monsoon

[Leslie Sanford]

Dario Solera wrote:

Dispose/Finalize is invoked automatically (but not necessarily immediately) when the instance goes out of scope.

I don't think Dispose is invoked automatically. I know the finalizer is, but by the time it's invoked, you can't count on any of the references in your object as still being valid. They may have already been collected. You can release unmanaged resources (which is important), but that's about it.

[Paul Watson]

I'm sure we can invent reasons to do it their way but in everyday coding at a business logic level I really do think an instance should be initialised to a common state on construction. Code runs in all manner of environments and they are not all equal. Rather have your code set the playing field than the environment.

regards, Paul Watson Ireland & South Africa

Shog9 wrote:

And with that, Paul closed his browser, sipped his herbal tea, fixed the flower in his hair, and smiled brightly at the multitude of cute, furry animals flocking around the grassy hillside where he sat coding Ruby on his Mac...

[Dario Solera]

Leslie Sanford wrote:

I don't think Dispose is invoked automatically. I know the finalizer is, but by the time it's invoked, you can't count on any of the references in your object as still being valid. They may have already been collected. You can release unmanaged resources (which is important), but that's about it.

You're right. Finalize is invoked non-deterministically, but Dispose must be called explicitly. My fault. :-O

If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Blog - My Photos - ScrewTurn Wiki

[Miszou]

Nemanja Trifunovic wrote:

constructors can't return values to tell us if something went wrong

I've recently started using a library that makes all constructors inaccessible, and all objects must be created by a overloads of a static Create method on the object. eg:

class MyClass
{
    private MyClass() {}

    public static MyClass Create()
    {
        return new MyClass();
    }
}

I first thought that this was because constructors could not return failure codes, but as I type this, I realize that a static Create method with a specific return type can't return a status code either! Then I thought it was for serializing the object or something of that nature, but with reflection (in .NET), you can call a constructor as easily as any other method. My final thoughts on this, are that the Create method does not have to return a specific instance, while a constructor does. This means that in a complex hierarchy, you can be given a descendent object instead of the object you asked actually asked for, depending on how the Create method works. A highly contrived example:

class ClassA
{
    private ClassA() {}

    public static ClassA Create( int x )
    {
        if ( x < 0 )
            return new ClassA();
        else
            return ClassB.Create();
    }
}

class ClassB : ClassA
{
    private ClassB() {}

    public static ClassB()
    {
        return new ClassB();
    }
}

static void main()
{
    ClassA myClass = ClassA.Create( 3 ); // Will really create a ClassB
}

Is this what it's used for? Or am I heading into La-La Land with this line of thinking?

---

Sunrise Wallpaper Project | The StartPage Randomizer | A Random Web Page

[ewasjdgb]

pbraun wrote:

There are very valid reasons to use them outside of the constructor as well

I think the term 'as well' qualifies it really. IMHO it's fine to call the init() outside of the constructor as well, but seems foolish to not to call it at construct time - even if all it does is initialise the object to a NULL state.

[Rama Krishna Vavilala]

I think it depends. Normally I would lean towards the constructor based initialization but not always. In the end you have to decide whether it improves code readability. Here is an horror story which ought to go to the Coding Horrors. In my previous company, I was fixing an issue and in that file I found the following code:

void PostInvoice()
{
ApbhTivhStatusChange * pChg = new ApbhTivhStatusChange(m_pContext);
delete pChg;

//Some other code follows this is where the real bug I was
//supposed to fix was
}

After fixing the issue, I removed the first 3 lines of the function thinking that it was not doing anything as the process function was commented out. My bug fix worked correctly and I checked it in. I modified like this:

void PostInvoice()
{
//Some other code follows this is where the real bug I was
//supposed to fix was
}

Later on is QA testing it was discovered that seem other piece of application functionality broke. It was embarrassing to find that the code I removed caused the issue. It was not a big issue to discover that the work was being done in the constructor and destructor of ApbhTivhStatusChange class.

class ApbhTivhStatusChange
{
private:
Context* m_pContext;

public:
ApbhTivhStatusChange(Context* pContext)
{
pContext->ConnectToDatabase();
pContext->BalanceInvoice();
}

~ApbhTivhStatusChange()
{
pContext->Cleanup();
}
}

The above code was poorly written even though it worked. It caused a huge confusion. But one thing is for sure, you should always add clean up code in the destructor. There are very few cases where I found that it is not advisable to do so and of course you need to make sure that the destructors do not throw any exceptions but at the same time they log the exceptions.

Co-Author ASP.NET AJAX in Action

[Phil Harding]

El Corazon wrote:

Others have promoted an init()/configure() methodology and cleanup()/clear() so that constructors construct the class, not the content, init()/configure() sets up the content, cleanup()/clear() removes the content

I find that argument totally bogus, the new operator creates an object instance, and then runs the constructor "over" that instance, the contructor is nothing more than a function which is automatically run when a new object instance is created, a constrructors raison d'etre is to initialise the object instance ready for use. By that score the constructor is badly named, it should have been called the initialiser :^)

---

- "I'm not lying, I'm just writing fiction with my mouth"

Phil Harding.
myBlog [^] | mySite [^]

[Janzen]

If you want to bring it up with the team again, and I would personally, the name of the pattern that you use is called Resource Acquisition Is Initialization. The best reason for using this pattern, in my opinion, is that it is exception safe. If an exception happens it the object will be cleaned up automatically when the destructor is called, without you having to specifically needing to call the cleanup method. A quick google search for RAII will bring up plenty of reasons to discuss with your team should you ever find yourself in that argument again.

[Bijesh]

Just to add on to what others have said, even with exceptions, in C++, an exception raised inside a constructor still poses a problem. For example, if you are using a pointer, and the constructor thew an exception, do you delete the object through that pointer? Is it needed/safe? It was safer to do just simple initialisations within the constructor, and put anything that can go wrong in a separate method.

[Rama Krishna Vavilala]

Bijesh wrote:

For example, if you are using a pointer, and the constructor thew an exception, do you delete the object through that pointer?

The object automatically gets deleted if the construtcor throws an exception and the VC++ compiler implements this feature correctly. That's is the reason why if you create a placement form of new operator you also need to create a matching placement form of delete operator.

Co-Author ASP.NET AJAX in Action

[Nemanja Trifunovic]

Bijesh wrote:

For example, if you are using a pointer, and the constructor thew an exception, do you delete the object through that pointer? Is it needed/safe?

That's why raw pointers are a bad idea. Use RAII[^] and life will be good :)

---

Programming Blog utf8-cpp

[Nemanja Trifunovic]

Janzen wrote:

the name of the pattern that you use is called Resource Acquisition Is Initialization.

Amen. Although it is surprising how many people refuse to grasp it.

---

Programming Blog utf8-cpp

[Big Daddy Farang]

Whoever wrote the original PostInvoice() and did not comment the purpose of the first two lines should be taken out and shot. BDF

[Rama Krishna Vavilala]

The code actually evolved passing through several developers, the original developer might have done it correctly. It was probably the idea of a later developer who was a newbie to use the constructor an destructor to do all the work.

Co-Author ASP.NET AJAX in Action

[El Corazon]

Rama Krishna Vavilala wrote:

The code actually evolved passing through several developers, the original developer might have done it correctly. It was probably the idea of a later developer who was a newbie to use the constructor an destructor to do all the work.

we had something like that happen to us. It was in an Ascii to Latitude/Longitude routine. I forget the name of the method, but it supported several types of latitude or longitude references (dd.decimal or dd mm.dec or dd mm ss.dec). Another programmer got ahold of the method and continued addition additional inputs beyond even latitude and longitude, attempting the equivalent generalality of a scanf() for geodetic values. Pass about 6 months and no one knew these changes occured and everything was still going fine, until we tried to run a specific data set in a specific format, and intermittent jumps were occuring in the data. Turns out the new changes were not thread-safe, and the routine had grown so complex supporting so many types that it was a pain to track down! mind you, the method was still directly referenced as something to the extent of ascii 2 latlong in the name, so everyone thought it still did just that.

_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)