Article View: borland.public.cppbuilder.nativeapi
Article #12557Re: Threads Threads Threads
From: Colin Maharaj
Date: Wed, 03 Dec 2003 03:03
Date: Wed, 03 Dec 2003 03:03
10 lines
1334 bytes
1334 bytes
> Maybe. Please show your actual code. Too messy and complicated sorry (boy I hate admitting this). > Which makes sense, since you introduced your own mechanism of protecting > thread A's resources from being accessed by thread B until it is actually > ready. But this mechanisim I use, is it a good OOP approach or is there another "better" way to do this.
Technical Details
Message-ID:
<3FCD5264.403C253A@cablenett.net>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<3FCBCCB2.C4C79E81@cablenett.net> <3fcbd0aa$3@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10cc67,e26628fb95e98199 X-Google-Attributes: gid10cc67,public X-Google-ArrivalTime: 2003-12-02 19:09:27 PST Message-ID: <3FCD5264.403C253A@cablenett.net> Date: Tue, 02 Dec 2003 23:03:00 -0400 From: Colin Maharaj <cbm@cablenett.net> Reply-To: cbm@cablenett.net X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: borland.public.cppbuilder.nativeapi Subject: Re: Threads Threads Threads References: <3FCBCCB2.C4C79E81@cablenett.net> <3fcbd0aa$3@newsgroups.borland.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit NNTP-Posting-Host: 196.32.37.68 X-Trace: newsgroups.borland.com 1070420605 196.32.37.68 (2 Dec 2003 19:03:25 -0700) Lines: 10 Path: arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail