220 26162 article Path: news.gmane.org!not-for-mail From: "'Jeffrey Yasskin' via ISO C++ Standard - Future Proposals" Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Any interest to adding audio support to the std library? Date: Fri, 3 Jun 2016 18:30:28 -0700 Lines: 124 Approved: news@gmane.org Message-ID: References: <5751B06A.4080501@mail1.stofanet.dk> <5290948.va25uYNizX@tjmaciei-mobl1> <1580229.cHEgQxCuA1@tjmaciei-mobl1> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1143d182f1c7e5053469c952 X-Trace: ger.gmane.org 1465003851 2772 80.91.229.3 (4 Jun 2016 01:30:51 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 4 Jun 2016 01:30:51 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDDM34EO6QDRBSG6ZC5AKGQEW4K3CNQ@isocpp.org Sat Jun 04 03:30:50 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 1b90QL-0007Id-TZ for gclcip-std-proposals@m.gmane.org; Sat, 04 Jun 2016 03:30:50 +0200 Original-Received: by mail-qk0-f198.google.com with SMTP id l185sf142663633qkc.0 for ; Fri, 03 Jun 2016 18:30:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isocpp-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject: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=HR0x9PlFxOhToW3ERDM8CP2Qps8Wv+MSwI9Z870jovw=; b=MDje6j0lXU0PviAf3ifCiofp8NjHKLiv+lUvRLu9taCPNAMpXx37ObrilR4bAqnBb4 S9PNIXKxcMP+0c03/7Bq9oq0gw3YFbDuldJU4IZKjxEBC8hmYCkC9Ggp2GqwBbKjQfsv luqA9Cx2Nst80RIPqKdcHmyLmgTOCwFX8twMDOn/1NgkWo2Hs3IHMaBsHidrydE2Qzon 2Cukf6568+2TjF0ZWvl3O4U2QVf1yiXajJ9QqDJt7MyYbQnP/o87YxUuFHHHBJdSQMM+ 4jBM+HIlcRttX5cKQjcl8Bkp6yrw46yPgwqMeFREe0+TNkFUFBWJNtczA9H6ZjgS61DH MGxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject: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=HR0x9PlFxOhToW3ERDM8CP2Qps8Wv+MSwI9Z870jovw=; b=JhXFWxj5nus3N0BQXUrz1E4e/Piv6jWdMBs6/xRMzzKEIQE/LSoXNQuwrGzyuPexY4 nd+7pjRLSe3v9eB7ye4MOIpI1G2z0lpoBYPQLTVipNxMet5KAnpjl4Zp/6aZ5s6cPBcb fJXlRBx9kqFCFIkJ65Ty7LDuUyBMgmCTpw+3j09HaCU96brWFfO76lYHtJXRAFpTfjXY zOzURyJW20CM28N054px8Tmqhq/rBbBgDkHpVFTmRDSLLVkbgVgr09LZDGEO2iEF7ZSP iPud1iW2l3c7O7B7X13pY3crNXHNuJ3yL5ZbIJhe0u2gvq3no7ddtVGH/FOA4+wxbHLU FD2A== X-Gm-Message-State: ALyK8tJz+5FF4d2l6oj5hJU0yvfKzoA9d5pyIhQ7YVoPvPkVaRZH/lbLF1eSWTubyVP7UA== X-Received: by 10.140.221.80 with SMTP id r77mr4852386qhb.16.1465003849086; Fri, 03 Jun 2016 18:30:49 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.36.127.87 with SMTP id r84ls122717itc.15.canary; Fri, 03 Jun 2016 18:30:48 -0700 (PDT) X-Received: by 10.107.58.213 with SMTP id h204mr9609510ioa.172.1465003848141; Fri, 03 Jun 2016 18:30:48 -0700 (PDT) Original-Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com. [2607:f8b0:4001:c0b::22f]) by mx.google.com with ESMTPS id f22si9362623iod.189.2016.06.03.18.30.48 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Jun 2016 18:30:48 -0700 (PDT) Received-SPF: pass (google.com: domain of jyasskin@google.com designates 2607:f8b0:4001:c0b::22f as permitted sender) client-ip=2607:f8b0:4001:c0b::22f; Original-Received: by mail-it0-x22f.google.com with SMTP id n126so6055226itd.1 for ; Fri, 03 Jun 2016 18:30:48 -0700 (PDT) X-Received: by 10.36.2.2 with SMTP id 2mr3482191itu.34.1465003847796; Fri, 03 Jun 2016 18:30:47 -0700 (PDT) Original-Received: by 10.64.225.228 with HTTP; Fri, 3 Jun 2016 18:30:28 -0700 (PDT) In-Reply-To: <1580229.cHEgQxCuA1@tjmaciei-mobl1> X-Original-Sender: jyasskin@google.com X-Original-Authentication-Results: mx.google.com; dkim=pass header.i=@google.com; spf=pass (google.com: domain of jyasskin@google.com designates 2607:f8b0:4001:c0b::22f as permitted sender) smtp.mailfrom=jyasskin@google.com; dmarc=pass (p=REJECT dis=NONE) header.from=google.com X-Original-From: Jeffrey Yasskin 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:26162 Archived-At: --001a1143d182f1c7e5053469c952 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, Jun 3, 2016 at 6:09 PM, Thiago Macieira wrote= : > On s=C3=A1bado, 4 de junho de 2016 02:20:15 BRT Andrey Semashev wrote: > > What is needed is a standardized interface for these different modules > > to work with each other. The interface should also allow me, the > > developer, to work with the media (e.g. create my own audio or image > > filter or a new codec or a new device driver). > > That I agree with. > > But should the standard mandate that there should be at least one? How do= es > someone write a plugin to the C++ Standard Library? Will we now mandate > this > kind of ability? > Yes. We already do this with things like the random engines. If not, then will there be a requirement that the C++ library vendor provid= e > it? If so, please think carefully how Apple should code libc++ to work on > iOS. > WebCrypto has an example of navigating a legal minefield for implementers. Also remember to leave the legal speculation to lawyers. It's good to have the heads-up that "hey lawyers should look at this", but anything more is unwise. Again, I think this is not material for the C++ Standard Library. > I think it's a great area for the C++ library to expand into. I'm definitely worried about the expertise of the people writing the proposal (e.g. if I proposed an audio library for C++, I should be laughed off the stage), but we can overcome that by asking well-known audio users for their opinions before standardizing the proposal. Jeffrey --=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/CANh-dX%3DheKaWzvE%2Brk8FeCSTQyZ8-FR9UaGdam8quLa= EuLJ%3D-A%40mail.gmail.com. --001a1143d182f1c7e5053469c952 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On F= ri, Jun 3, 2016 at 6:09 PM, Thiago Macieira <= thiago@macieira.org> wrote:
On s=C3=A1bado, 4 de junho de 2016 02:20:15 BRT Andrey Semashev= wrote:
> What is needed is a standardized interface for these different modules=
> to work with each other. The interface should also allow me, the
> developer, to work with the media (e.g. create my own audio or image > filter or a new codec or a new device driver).

That I agree with.

But should the standard mandate that there should be at least one? How does=
someone write a plugin to the C++ Standard Library? Will we now mandate thi= s
kind of ability?

Yes. We already do thi= s with things like the random engines.

If not, then will there be a requirement that the C++ library vendor provid= e
it? If so, please think carefully how Apple should code libc++ to work on i= OS.

WebCrypto has an example of=C2=A0na= vigating a legal minefield for implementers.

A= lso remember to leave the legal speculation to lawyers. It's good to ha= ve the heads-up that "hey lawyers should look at this", but anyth= ing more is unwise.

Again, I think this is not material for the C++ Standard Library.

I think it's a great area for the C++ libra= ry to expand into. I'm definitely worried about the expertise of the pe= ople writing the proposal (e.g. if I proposed an audio library for C++, I s= hould be laughed off the stage), but we can overcome that by asking well-kn= own audio users for their opinions before standardizing the proposal.
=

Jeffrey

--
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/CANh-dX%3Dh= eKaWzvE%2Brk8FeCSTQyZ8-FR9UaGdam8quLaEuLJ%3D-A%40mail.gmail.com.
--001a1143d182f1c7e5053469c952-- .