220 26316 <8842319.5S1MoY7pmH@lastique-pc> article Path: news.gmane.org!not-for-mail From: Andrey Semashev Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Any interest to adding audio support to the std library? Date: Mon, 13 Jun 2016 15:05:25 +0300 Lines: 103 Approved: news@gmane.org Message-ID: <8842319.5S1MoY7pmH@lastique-pc> References: <5751B06A.4080501@mail1.stofanet.dk> <2897526.WjqoZ8n3I9@lastique-pc> <8DC89BEC-9ED2-4268-9D12-77D7C57128CC@gmail.com> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="nextPart1881748.xZfsF50Y85" Content-Transfer-Encoding: 7Bit X-Trace: ger.gmane.org 1465819540 23022 80.91.229.3 (13 Jun 2016 12:05:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 13 Jun 2016 12:05:40 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCXY5TXHWYJRBC6D7K5AKGQEWOVUSDI@isocpp.org Mon Jun 13 14:05:33 2016 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-wm0-f69.google.com ([74.125.82.69]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bCQcW-0003uy-U0 for gclcip-std-proposals@m.gmane.org; Mon, 13 Jun 2016 14:05:32 +0200 Original-Received: by mail-wm0-f69.google.com with SMTP id 4sf28108173wmz.1 for ; Mon, 13 Jun 2016 05:05:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isocpp-org.20150623.gappssmtp.com; s=20150623; h=from:to:subject:date:message-id:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=dUzCjHMaX6CZ177wwSFEF/gFQqnhXCwgsd8tqIixLoY=; b=qC73C7u/Jq3wIjLe0oGifNc48t19MCkw8WaBNmIH7aiudIRWT61BA5k59AG/PESLO0 QIPrO7CyTMza0XHcZATFHjkxuhbAQGh3Idmu5mQFBH0TcESBJSRSJCzVJIc+RPfGuwf1 r3nBgVFH+h+4M5LIYu/ggloPZRBgK/H0mc1KDq1EGhEt4ZAhP6GJ6C/C/WTvWXnZkKkL 5G0IWybgE1oBFyeZ9elhHIlmcoxS4tXag319jS0sWKwkXUjANIo1g+04Tr4MiXFTRQcK 01BQpRDoDn2FJu4jYdHZQPckUVSeY+t03Hfv8T7JSCBYoht2I1/WRLbrF4ToGReuAYEZ X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=dUzCjHMaX6CZ177wwSFEF/gFQqnhXCwgsd8tqIixLoY=; b=YRtEbN99kl3EfS4Vjv9nexduF8H0w8I07KHDYgF/It2FmfHud72fvJTnqZo4oDdyr+ T24x5CdC8g+oWG9EL1hsUjfCGkdS6vCYQF+CpWTPvHuKrY9pGhgslq3QptJd7YlzzKIg GsN4OYPdae0wqIsgORPYKBv+Llp2dU5/UYhkQcyCVPT70yJi8hyfj/jUo6XiwOSGWtss 7hgJNK+X2uC9Q6ebUdFA6y0eAq0+5HF2Js5RH5HbpqtFlicByc3oGTeXX79SVWbT+RpC L9W96CjQcygqTcSGmOUQFElYyyvGq5Ok9rg9bRofaYSlU0XZ8h68eE5wpggXhLXfqOB6 X-Gm-Message-State: ALyK8tIeybB56clJgc2gDuhrRGwD79c69xNvETkVLuqEtyc5ub+DpVOFEr5TmIzKTjKATQ== X-Received: by 10.28.38.196 with SMTP id m187mr147757wmm.4.1465819532104; Mon, 13 Jun 2016 05:05:32 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.25.168.85 with SMTP id r82ls217659lfe.34.gmail; Mon, 13 Jun 2016 05:05:30 -0700 (PDT) X-Received: by 10.25.91.76 with SMTP id p73mr164578lfb.181.1465819527950; Mon, 13 Jun 2016 05:05:27 -0700 (PDT) Original-Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com. [2a00:1450:4010:c07::233]) by mx.google.com with ESMTPS id ld9si11344493lbc.87.2016.06.13.05.05.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Jun 2016 05:05:27 -0700 (PDT) Received-SPF: pass (google.com: domain of andrey.semashev@gmail.com designates 2a00:1450:4010:c07::233 as permitted sender) client-ip=2a00:1450:4010:c07::233; Original-Received: by mail-lf0-x233.google.com with SMTP id u74so83092758lff.2 for ; Mon, 13 Jun 2016 05:05:27 -0700 (PDT) X-Received: by 10.25.19.204 with SMTP id 73mr183870lft.24.1465819527500; Mon, 13 Jun 2016 05:05:27 -0700 (PDT) Original-Received: from lastique-pc.localnet (broadband-90-154-68-136.nationalcablenetworks.ru. [90.154.68.136]) by smtp.googlemail.com with ESMTPSA id g22sm825604lji.43.2016.06.13.05.05.26 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 13 Jun 2016 05:05:26 -0700 (PDT) User-Agent: KMail/5.1.3 (Linux/4.4.0-24-generic; KDE/5.18.0; x86_64; ; ) In-Reply-To: <8DC89BEC-9ED2-4268-9D12-77D7C57128CC@gmail.com> X-Original-Sender: andrey.semashev@gmail.com X-Original-Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com; spf=pass (google.com: domain of andrey.semashev@gmail.com designates 2a00:1450:4010:c07::233 as permitted sender) smtp.mailfrom=andrey.semashev@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: X-Spam-Checked-In-Group: std-proposals@isocpp.org 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:26316 Archived-At: This is a multi-part message in MIME format. --nextPart1881748.xZfsF50Y85 Content-Type: text/plain; charset=UTF-8 On Monday, 13 June 2016 14:55:43 MSK alexander.zywicki@gmail.com wrote: > If that should be the case we would have to write a type trait that makes > sure that the user supplied clock was an acceptable clock source. I'm not sure we need a trait for checking the clock for acceptance. > I suggest > using the built in ones for the mean time because the std makes certain > guarantees about those clocks that can make sure that thy meet our needs. > Not to mention that a default would be needed even if we allowed user > supplied clocks The problem I have with std::chrono::steady_clock is that it's not guaranteed to be equivalent to CLOCK_MONOTONIC. Or any other POSIX clock type. It may work as a default clock type, should we decide one is needed, but IMO it should be customizable from the start. -- 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. To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/8842319.5S1MoY7pmH%40lastique-pc. --nextPart1881748.xZfsF50Y85 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8

On Monday, = 13 June 2016 14:55:43 MSK alexander.zywicki@gmail.com wrote:

> If tha= t should be the case we would have to write a type trait that makes

> sure t= hat the user supplied clock was an acceptable clock source.

&nb= sp;

I'm not sur= e we need a trait for checking the clock for acceptance.

&nb= sp;

> I sugg= est

> using = the built in ones for the mean time because the std makes certain

> guaran= tees about those clocks that can make sure that thy meet our needs.

> Not to= mention that a default would be needed even if we allowed user

> suppli= ed clocks

&nb= sp;

The problem= I have with std::chrono::steady_clock is that it's not guaranteed to be eq= uivalent to CLOCK_MONOTONIC. Or any other POSIX clock type. It may work as = a default clock type, should we decide one is needed, but IMO it should be = customizable from the start.

&nb= sp;

--
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-proposa= ls+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/= d/msgid/std-proposals/8842319.5S1MoY7pmH%40lastique-pc.
--nextPart1881748.xZfsF50Y85-- .