Delphi – TThread.resume is deprecated in Delphi-2010 what should be used in place

delphidelphi-2010

In my multithread application

I use TThread.suspend and TThread.resume

Since moving my application to Delphi 2010 I get the following warring message

[DCC Warning] xxx.pas(277): W1000 Symbol ‘Resume’ is deprecated

If Resume is deprecated what should be used in place?

EDIT 1:

I use the Resume command to start the thread – as it is Created with 'CreateSuspended' set to True and Suspend before I terminate the thread.

EDIT 2:

Here is a link the delphi 2010 manual

Best Answer

Charles if do you read the code of TThread class , do you find the answer.

   TThread = class  
   private type  

..
..
..   
   public  
     constructor Create(CreateSuspended: Boolean);  
     destructor Destroy; override;  
     procedure AfterConstruction; override;  
     // This function is not intended to be used for thread synchronization.  
     procedure Resume; deprecated;  
     // Use Start after creating a suspended thread.  
     procedure Start;  
     // This function is not intended to be used for thread synchronization.  
     procedure Suspend; deprecated;  
     procedure Terminate;

See this link RAD Studio 2010: Community pulse: The day after. (Part 2)

Edit:

If you need to synchronize threads, you can use a scheme based on TMutex, TEvent and critical sections.

Bye.

Related Solutions

R – How long has EStackOverflow been deprecated and what replaces it

I don't have D5 here to say, but I barely remember the deprecated directive appeared only on D6.

As for StackOverflow exception, I think it's deprecated because is only for Delphi runtime environment to raise it.

EDIT: Based on the aggregate of all the answers, EStackOverflow was deprecated in Delphi 6 when the Deprecated keyword was introduced.

Delphi – Which is the correct way to start a suspended thread in delphi 2007

The correct way to start a suspended thread is to never have a suspended thread in the first place.

There's a better way to create threads. If the caller must provide a value to the object in order for the class to work correctly, then don't make it optional: Require it as a parameter to the constructor. And if there's only one valid value for that parameter, then don't even make it a parameter: Just hard-code it in the constructor. (How many times have you written a thread class that only sometimes should free itself on termination? I've never seen that.)

constructor TMyThread.Create(Prop1, Prop2: Integer);
begin
  inherited Create(False);
  FreeOnTerminate := True;
  Property1 := Prop1;
  Property2 := Prop2;
end;

Then you can use the Ron Popeil method of creating threads: Just set it and forget it!

MyThread := TMyThread.Create(900, 2);

The caller doesn't have to do anything with the thread after creating it. And since it's a free-on-terminate thread, it's possible that the caller shouldn't even keep a reference to the MyThread variable at all since the reference will become invalid as soon as the thread finishes running.

(Worried about that inherited Create(False) line creating a thread that's going to start running before the rest of the constructor finishes running? Don't be! That was fixed in Delphi 6, over a decade ago. The thread will automatically start itself after the constructor finishes; see TThread.AfterConstruction to see how.)

Best Answer

Related Solutions

R – How long has EStackOverflow been deprecated and what replaces it

Delphi – Which is the correct way to start a suspended thread in delphi 2007

Related Topic