TCriticalSection (Solved)

[xenblaise]

Why is it

Illegal qualifier

type
Tmyfunc = function(mem:tmemorystream; prec:pMyStreamRec; score:integer): integer of object;
TScanThread=class(TThread)
private
  FCS:TCriticalSection;
  FIndex:integer;
protected
    procedure execute; override;
public
    constructor Create(AIndex:integer);
    destructor Destroy; override;
end;

implementation

{ TScanThread }
constructor TScanThread.Create(AIndex:integer);
begin
  FCS:=TCriticalSection.Create; // ILLEGAL QUALIFIER, why?
  FIndex:=AIndex;
  inherited Create(true);
end;

destructor TScanThread.Destroy;
begin
  freeandnil(FCS);
  inherited;
end;


Thanks

[typo]

Code: [Select]

TCRITICALSECTION = TRTLCriticalSection;
and

Code: [Select]

TRTLCriticalSection = packed record
    DebugInfo : pointer;
    LockCount : longint;
    RecursionCount : longint;
    OwningThread : THandle;
    LockSemaphore : THandle;
    SpinCount : ULONG_PTR;
  end;       

[Leledumbo]

Code: [Select]

TCriticalSection.Create;This calls TCriticalSection's constructor IF it's a class.

Code: [Select]

TCRITICALSECTION = TRTLCriticalSection;
TRTLCriticalSection = packed record
    DebugInfo : pointer;
    LockCount : longint;
    RecursionCount : longint;
    OwningThread : THandle;
    LockSemaphore : THandle;
    SpinCount : ULONG_PTR;
  end;As you post here, it's a packed record, NOT a class.

[marcov]

It is also a class, just in a different unit. (syncobjs)

Put "syncobjs" as last unit in the uses clause in your original code and it will work.

This is a common confusion for people that come from older Delphi's, with more recent Delphi's (D7+ iirc), this class moved to syncobjs too

See e.g.

http://docwiki.embarcadero.com/VCL/en/SyncObjs.TCriticalSection

[xenblaise]

Thanks

"syncobjs" did solved the issue.

[Eko Wahyudin]

// ILLEGAL QUALIFIER, why?

because there is two or more same symbol name on different unit.

eg. you have a variable on unit1;
unit unit1;
interface
var x: Integer;

unit unit2;
interface
var x: string;

and you use unit1 and unit2;

uses unit1, unit2;

then x:= 'hallo world';

it's will be error;


you can use code like this for your code

varCriticalSection := syncobjs.TCritialSection.Create;

[Leledumbo]

and you use unit1 and unit2;

uses unit1, unit2;

then x:= 'hallo world';

it's will be error;

Nope, it will be compiled OK. Identifiers are searched backward from the uses clause list. In this case, x is the same as unit2.x, which is indeed a string.