220 26321 article Path: news.gmane.org!not-for-mail From: alexander.zywicki@gmail.com Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Any interest to adding audio support to the std library? Date: Mon, 13 Jun 2016 10:52:35 -0500 Lines: 154 Approved: news@gmane.org Message-ID: References: <5751B06A.4080501@mail1.stofanet.dk> <2897526.WjqoZ8n3I9@lastique-pc> <8DC89BEC-9ED2-4268-9D12-77D7C57128CC@gmail.com> <8842319.5S1MoY7pmH@lastique-pc> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 (1.0) Content-Type: multipart/alternative; boundary=Apple-Mail-7AEC68FB-A09A-40B6-BDDD-7AFBFBDAAFFD Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1465833169 25578 80.91.229.3 (13 Jun 2016 15:52:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 13 Jun 2016 15:52:49 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBCS7TY6DTQOBBRVN7O5AKGQEKJCJ2AQ@isocpp.org Mon Jun 13 17:52:40 2016 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-qk0-f198.google.com ([209.85.220.198]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bCUAK-0006xw-IF for gclcip-std-proposals@m.gmane.org; Mon, 13 Jun 2016 17:52:40 +0200 Original-Received: by mail-qk0-f198.google.com with SMTP id z142sf121830631qkb.0 for ; Mon, 13 Jun 2016 08:52:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isocpp-org.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to :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=8g7OX7Vfg8hCy+PJWlRrb0Kw28k5H3C/arv8gjtgKIo=; b=jslZIIJtMqM/3Fz2G9Epd4j+HfJhRBzBV3APJltwtYVnsVR0E23u1iPKpJ0ci6v6Rt v8n1KNLbsxsU6yJIiNy3Tw/gFK+HgspZ6sy1nHRV3HfAdlwSUDtlH6K11CHWBV0N4dRJ csqjBOQhwkaBj+3hoquCITDBxojZs5RgTuiupdQR5DIwzEl5Vo864PCE4FY79GQI/nUO rT0Vpd/P7d4rM4BzR20pgRwo/9WOC2ZaD2WQR3I0hSOSJ00KlnzSorkkIeKZBrgNc81y WcPIS71483lEEHttD1Xva57OuMGSnjfHO27cDXafo5jv+E8eMFTMJnF86FWM6r5GOrVL 9z9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to :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=8g7OX7Vfg8hCy+PJWlRrb0Kw28k5H3C/arv8gjtgKIo=; b=HfsB9BthGZhvRyIPV7AJ0/zyzLMTob0nREs6r2lNuS5n1DB3g5WI7EFBWJBLAdrCA9 iRKXxTj63hmyl0CPQF33/vlOaBUmSobS8X8wwZS53x5u6b6cNi3kAtrzXt6Iy1ACVB0J GVBvAHYEaTMkE2l9Ax4vW0ZE8kY0/WuTVE/h+MJzHiCe3g6DcX4qNTU8mixTsExBsgKH XUw6fquMYdXfdkBpCw77swiFtU/5sD11CiqqA6O+Jkn559P2Nhz+QZIkPu7QB9raWi6K KGfXIAjm726jVkd237c8Cr8eUjKDJWnv5WKZ78Pl0ZPKeKdIPP53JktJRzdoKjqchMb5 PUb X-Gm-Message-State: ALyK8tIwbPHC/+WUB4pTcTJ90vtP0uVhV0zvGw3rjNusPq8lXoRClT133sWebR5Fe3aeBg== X-Received: by 10.129.120.8 with SMTP id t8mr8037546ywc.58.1465833159641; Mon, 13 Jun 2016 08:52:39 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.36.3.198 with SMTP id e189ls956249ite.22.gmail; Mon, 13 Jun 2016 08:52:38 -0700 (PDT) X-Received: by 10.107.149.66 with SMTP id x63mr23658583iod.141.1465833158448; Mon, 13 Jun 2016 08:52:38 -0700 (PDT) Original-Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com. [2607:f8b0:4001:c06::22c]) by mx.google.com with ESMTPS id z18si11934199iof.4.2016.06.13.08.52.38 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Jun 2016 08:52:38 -0700 (PDT) Received-SPF: pass (google.com: domain of alexander.zywicki@gmail.com designates 2607:f8b0:4001:c06::22c as permitted sender) client-ip=2607:f8b0:4001:c06::22c; Original-Received: by mail-io0-x22c.google.com with SMTP id d2so36322756iof.0 for ; Mon, 13 Jun 2016 08:52:38 -0700 (PDT) X-Received: by 10.107.19.169 with SMTP id 41mr26408114iot.11.1465833158228; Mon, 13 Jun 2016 08:52:38 -0700 (PDT) Original-Received: from [10.43.249.119] ([166.175.187.92]) by smtp.gmail.com with ESMTPSA id g98sm12098123ioj.11.2016.06.13.08.52.36 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 13 Jun 2016 08:52:36 -0700 (PDT) X-Mailer: iPhone Mail (13F69) In-Reply-To: <8842319.5S1MoY7pmH@lastique-pc> X-Original-Sender: alexander.zywicki@gmail.com X-Original-Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com; spf=pass (google.com: domain of alexander.zywicki@gmail.com designates 2607:f8b0:4001:c06::22c as permitted sender) smtp.mailfrom=alexander.zywicki@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:26321 Archived-At: --Apple-Mail-7AEC68FB-A09A-40B6-BDDD-7AFBFBDAAFFD Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable It may not match any posix monotonic clock type but it is specified to be m= onotonic as far as I remember( at least going off of http://en.cppreference= ..com/w/cpp/chrono/steady_clock) I will dig through the std eventually to do= uble check. As long as the is_steady is set to true it will work for this c= ontext > On Jun 13, 2016, at 7:05 AM, Andrey Semashev = wrote: >=20 > 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 mak= es > > sure that the user supplied clock was an acceptable clock source. > =20 > I'm not sure we need a trait for checking the clock for acceptance. > =20 > > 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 need= s. > > Not to mention that a default would be needed even if we allowed user > > supplied clocks > =20 > The problem I have with std::chrono::steady_clock is that it's not guaran= teed 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. > =20 > --=20 > You received this message because you are subscribed to a topic in the Go= ogle Groups "ISO C++ Standard - Future Proposals" group. > To unsubscribe from this topic, visit https://groups.google.com/a/isocpp.= org/d/topic/std-proposals/Hkdh02Ejx6s/unsubscribe. > To unsubscribe from this group and all its topics, send an email to std-p= roposals+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/isoc= pp.org/d/msgid/std-proposals/8842319.5S1MoY7pmH%40lastique-pc. --=20 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 e= mail 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/DB2ADD2C-9975-4545-8379-9BF5088F7FB2%40gmail.com= .. --Apple-Mail-7AEC68FB-A09A-40B6-BDDD-7AFBFBDAAFFD Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It may not match any po= six monotonic clock type but it is specified to be monotonic as far as I re= member( at least going off of http://en.cppreference.com/w/cpp/chrono/steady_clo= ck) I will dig through the std eventually to double check. As long as t= he is_steady is set to true it will work for this context

On = Jun 13, 2016, at 7:05 AM, Andrey Semashev <andrey.semashev@gmail.com> wrote:

On Monday, = 13 June 2016 14:55:43 MSK al= exander.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 a topic in the Goog= le Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this topic, visit https://groups.= google.com/a/isocpp.org/d/topic/std-proposals/Hkdh02Ejx6s/unsubscribe.<= br> To unsubscribe from this group and all its topics, 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.

--
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.c= om/a/isocpp.org/d/msgid/std-proposals/DB2ADD2C-9975-4545-8379-9BF5088F7FB2%= 40gmail.com.
--Apple-Mail-7AEC68FB-A09A-40B6-BDDD-7AFBFBDAAFFD-- .