TThreads & standard C library calls

TThreads & standard C library calls

Post by CC » Sun, 17 Aug 2003 07:11:39

Greetings All.
I have a TThread'ed program that uses open() close() access() and other
standard C library calls within the TThread object.

I was wondering if anyone knows if doing this is thread safe with the
standard library functions? Not sure how the winapi under neath implements
these functions.

Thanks for the assistance,

1. standard libraries don't behave like standard 'libraries'

2. A Policy for Inclusion in the Standard Library: was Modules forinclusion in standard library?

Yes. Users also indicate practical (versus theoretical) usefullness and
also test beyond what a developer might (especially documentation).

Of course, modules written by the inner core group of active developers or
on their behalf may bypass these criteria, but the context of my answer was
discussion of inclusion of existing modules mostly or all written by other

Part of the maintainence requirement is a willingness to work compatibly
with the Python release cycle. Related to that is something I left out on
the other side: willingness to license the module to the PSF for inclusion.
Some people seem to assume that everyone 'of course' wants their stuff
included and that it is just Guido blocking inclusion, but that just is not

Terry J. Reedy

3. A Policy for Inclusion in the Standard Library: was Modules for inclusion in standard library?

4. Using simultaneously TThread::Synchronize() with TThread::Suspend()

5. [Simulink, S-functions] Calling Lapack++ library from a library called by a S-function

6. How to call call a MATLAB shared library from another shared library

7. Cost of calling a standard library function

8. MASM32 Programmers can now call HLA Standard Library routines

9. MASM32 Programmers can now call HLA Standard Library Routines

10. Is there standard(POSIX) library call for timezone manipulation?

11. .NET equilavent to C's backtrace(), or How do I find a calling function?

12. It's not like C's preprocessor, it's more like a call to RegEx.

13. system call, library call, booty call, whatever.

14. Call for Advanced TThread Implementations

15. Query Interface failing when called from a TThread