• strtr (18/18) Jun 24 2010 void externalFunc(){}
• marksibly (3/3) Jun 24 2010 Hi,
• Simen kjaeraas (4/22) Jun 25 2010 A reference to it will still be on the stack, so it should be no problem...
• strtr (2/26) Jun 25 2010 The "this" marksibly mentioned. Thanks peoples ;)

strtr <strtr sp.am> writes:

void externalFunc(){}

class C
{
  ..
  int index_;
  int yay;
  void removeMe()
  {
    //remove last reference to this object
    objects[_index] = null;

    //other critical code
    memberFunc();
    externalFunc();
  }
  void memberFunc(){yay++}
}

Is there anything unsafe about his code? Like the GC removing the Object
before calling memberFunc..

marksibly <blitzmunter gmail.com> writes:

Hi,

Shouldn't be as 'this' will keep the object alive as long as necessary.

Mark

"Simen kjaeraas" <simen.kjaras gmail.com> writes:

strtr <strtr sp.am> wrote:

 void externalFunc(){}

 class C
 {
   ..
   int index_;
   int yay;
   void removeMe()
   {
     //remove last reference to this object
     objects[_index] = null;

     //other critical code
     memberFunc();
     externalFunc();
   }
   void memberFunc(){yay++}
 }

 Is there anything unsafe about his code? Like the GC removing the Object
 before calling memberFunc..

A reference to it will still be on the stack, so it should be no problem.

-- 
Simen

strtr <strtr sp.am> writes:

== Quote from Simen kjaeraas (simen.kjaras gmail.com)'s article
 strtr <strtr sp.am> wrote:
 void externalFunc(){}

 class C
 {
   ..
   int index_;
   int yay;
   void removeMe()
   {
     //remove last reference to this object
     objects[_index] = null;

     //other critical code
     memberFunc();
     externalFunc();
   }
   void memberFunc(){yay++}
 }

 Is there anything unsafe about his code? Like the GC removing the Object
 before calling memberFunc..

 A reference to it will still be on the stack, so it should be no problem.

The "this" marksibly mentioned. Thanks peoples ;)