delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/08/05/18:10:23

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Sat, 6 Aug 2005 00:10:05 +0200 (CEST)
From: Vaclav Haisman <V DOT Haisman AT sh DOT cvut DOT cz>
To: cygwin AT cygwin DOT com
Subject: What is the point of create_thread_and_wait()?
Message-ID: <20050805234708.P84746@logout.sh.cvut.cz>
MIME-Version: 1.0
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

What is the point of create_thread_and_wait() in fhandler_netdrive::exists()?
Or anywhere at all? Why spawning a thread at all when we have to wait for the
task to finish immediately after it is started? I really would like to know,
even though it is probably just lack of knowledge on my side.

VH


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019