Help needed about freeing async functions and pointers

[nikel]

Hi, how can I free this function:

Code: Pascal  [Select][+][-]

1. procedure TForm1.RunUpdaterAsync(Data: IntPtr);
2. begin
3.   RunShellExecute('updatecheck.exe', '', 1);
4.   Data:=0;
5. end;
6. ...
7. Application.QueueAsyncCall(@RunUpdaterAsync, FCounter);

[ASerge]

Hi, how can I free this function:

What is "free"? Application.RemoveAsyncCalls(Self)?

[avra]

I do not see from your example what should be freed. If you wanted to pass some data to a function called by QueueAsyncCall and later free it without leaking, then maybe you might want to check this where whole record is passed: https://forum.lazarus.freepascal.org/index.php/topic,38851.msg265181.html#msg265181

[nikel]

Sorry pointers make me frightened. I'm confused.

[lucamar]

Code: Pascal  [Select][+][-]

1. procedure TForm1.RunUpdaterAsync(Data: IntPtr);

Shouldn't that be:

Code: Pascal  [Select][+][-]

1. procedure TForm1.RunUpdaterAsync(Data: PtrInt);

???

As for how to free it (if it represents a pointer), that depends of what you pass to it but the most common ways are:

• Using Dispose(PThePointerType(Data)) for "normal" types dynamically instanced;
• Using PTheClass(Data)^.Free if it's a dynamic object; or
• Leave it alone if it points to a global var (of any type).

Also, note that your "Data := 0" does absolutely nothing (from a logic point of view): since the parameter is neither var or out, all it does is set the local copy to zero.

[giahung1997]

Sometimes I love C's int* more than Pascal PtrInt 

[Mr.Madguy]

There is nothing to be freed here. Callback is static and passed as pointer. It's not object, like in script languages. Data can be freed, if it's object, but it isn't. May be you mean abandon async call? Or abandon executed application?

[Thaddy]

Sometimes I love C's int* more than Pascal PtrInt 

Yeah, wild card programming would be easy.....

(Anyway, a bit more serious: release any objects in the thread it was created in the first place. That's the "law".)

[marcov]

Sometimes I love C's int* more than Pascal PtrInt 

ptrint is the equal of C99 intptr_t, not of *int, iow an integer with the same size as pointer.

[marcov]

There is nothing to be freed here. Callback is static and passed as pointer.

Callbacks are always pointers or records of pointers (in the case of nested or procedure of object). The @ here is a mode fpc/objfpc "feature" to disambiguate some rare cases. It doesn't really do anything then confirm you really want to pass that identifier as the callback .

The corner case is one you have a callback returning a procedure type of the same type (or compatible on some level) as the callback.

In mode delphi or TP you wouldn't use it.

[giahung1997]

Sometimes I love C's int* more than Pascal PtrInt 

Yeah, wild card programming would be easy.....

(Anyway, a bit more serious: release any objects in the thread it was created in the first place. That's the "law".)

Pascal is wordy and C is just compact. I love it simplicity until thing got complicated and need libraries. I hate underscores so much set_abc_xyz blah blah   

[giahung1997]

Sometimes I love C's int* more than Pascal PtrInt 

ptrint is the equal of C99 intptr_t, not of *int, iow an integer with the same size as pointer.

Ok. Sorry for my ignorant. The C we teach at school in my country is C89, fsck, people going to have C20