🚀 go-pugleaf

"CC" <Xcurtc@tmscorp.com> wrote in message
news:3f3d5dfa$1@newsgroups.borland.com...

> I was wondering if within a TTHread,
> is it ok to use the winapi:
>   EnterCriticalSection();
>   LeaveCriticalSection();
>   InitializeCriticalSection();
>
> Calls?

Of course.  TThread simply wraps an API thread object.  Critical Sections
are designed to be used with threads, particularly with multiple threads
accessing them at the same time.

> I have a tthread program, which I suspect is having
> problems somewhere with multiple threads running
> non-thread safe code.

Always a source of potential problems.

> I wanted to do something like:
> EnterCriticalSection(...);
> // read a file here, read from socket, close file, etc
> LeaveCriticalSection();

That is perfectly fine.

> I would imaging the synchronize uses these calls.

Only in BCB6.  In BB1-5, it does not use any API synchronization objects at
all.  It uses its own custom mechanism utilizing window messages instead.

> The problems w/synchronize you cant pass arguments, etc to sync. function.

That is only partially true.  Although you cannot pass any parameters when
calling Synchronize() itself, you can store the desired values into separate
variables which the synched method can then use once it is executed, ie:

    AnsiString MyStr = "whatever";
    int MyInt = 50;

    ...
    Synchronize(SomeMethod);
    ...

    void __fastcall TMyThread::SomeMethod()
    {
        // use MyStr and MyInt as needed
    }



Gambit