220 4749 <9b77805b-9e58-41ee-8918-40d726a1a006@isocpp.org> article Path: news.gmane.org!not-for-mail From: Jonathan Wakely Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: lock free traits for functions Date: Thu, 30 May 2013 04:29:54 -0700 (PDT) Lines: 62 Approved: news@gmane.org Message-ID: <9b77805b-9e58-41ee-8918-40d726a1a006@isocpp.org> References: <4ed4041c-a458-4fc8-ae3d-7534d5d261c2@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_249_8538835.1369913394463" X-Trace: ger.gmane.org 1369913399 3030 80.91.229.3 (30 May 2013 11:29:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 30 May 2013 11:29:59 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCMONUNYS4IRBNHQTSGQKGQETESMPWQ@isocpp.org Thu May 30 13:29:58 2013 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-qa0-f70.google.com ([209.85.216.70]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Ui13O-00039t-84 for gclcip-std-proposals@m.gmane.org; Thu, 30 May 2013 13:29:58 +0200 Original-Received: by mail-qa0-f70.google.com with SMTP id ii15sf552045qab.5 for ; Thu, 30 May 2013 04:29:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-beenthere:date:from:to:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe:content-type; bh=gLX4bZc7ndkYi90YR+kiaNkiIQcJoy3l6SQ0cPnMLfI=; b=VUxMZBy9UYUQZrQjwXngmP+l9WeIkaO0AiA7GMTv8TThyhANZjTMgEAOPw8WQSRfBq bQDjhD9PvIVw1SmdNy/cbf4Ddp3olu2R39K51oGCn2AgxRhpXoT0i9QcjNciAdyWE1Fb 2OqCakNegn7EUQ8vdQqRl/ynwHHm5I0tko6Hsitd2p+qJ/gBAroOPTQu5KIy2YItsUu8 YEMlcCOhtnXD5qD1BfOtDGy5m8ehTRn3QoWN3XWuTmYSlAXO/JVg6uSKWq4fUKqditAP npyGjb3J5eVjtk/K2Ssuo+c+49Bd4Mf5oF5n1Kigm58YPb4gP3Zl/1bTfcxIRmEN1j3N /OAg== X-Received: by 10.224.205.138 with SMTP id fq10mr4044660qab.1.1369913397193; Thu, 30 May 2013 04:29:57 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.49.4.1 with SMTP id g1ls283809qeg.64.gmail; Thu, 30 May 2013 04:29:55 -0700 (PDT) X-Received: by 10.49.87.70 with SMTP id v6mr548609qez.25.1369913395011; Thu, 30 May 2013 04:29:55 -0700 (PDT) In-Reply-To: X-Original-Sender: cxx@kayari.org Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: X-Google-Group-Id: 399137483710 List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:4749 Archived-At: ------=_Part_249_8538835.1369913394463 Content-Type: text/plain; charset=ISO-8859-1 So you're asking for standard library implementors to provide the answer for every function in the std::lib (I would object strongly to being required to do that) and that would only help for functions in namespace std, it wouldn't give you an answer for system functions not defined by the C++ standard e.g. POSIX functions such as ::usleep() and ::pthread_self(), and even if you convince ever C and OS library vendor to implement it, that wouldn't help for third-party libraries such as X toolkits or OpenGL libraries or Boost libraries or the thousands of other libraries. So would it actually be useful? It seems like it would be easier for you to just do some homework to find out if the functions you need to use are lock-free on the platforms you actually use, instead of pushing the work into the standard. -- --- You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group. To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org. To post to this group, send email to std-proposals@isocpp.org. Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/?hl=en. ------=_Part_249_8538835.1369913394463 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable So you're asking for standard library implementors to provide the answer fo= r every function in the std::lib (I would object strongly to being required= to do that) and that would only help for functions in namespace std, it wo= uldn't give you an answer for system functions not defined by the C++ stand= ard e.g. POSIX functions such as ::usleep() and ::pthread_self(), and even = if you convince ever C and OS library vendor to implement it, that wouldn't= help for third-party libraries such as X toolkits or OpenGL libraries or B= oost libraries or the thousands of other libraries.  So would it actua= lly be useful?  It seems like it would be easier for you to just do so= me homework to find out if the functions you need to use are lock-free on t= he platforms you actually use, instead of pushing the work into the standar= d.


--
 
---
You received this message because you are subscribed to the Google Groups &= quot;ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-pro= posals/?hl=3Den.
 
 
------=_Part_249_8538835.1369913394463-- .