220 26161 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: Fri, 3 Jun 2016 18:26:04 -0700 (PDT) Lines: 66 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/mixed; boundary="----=_Part_1136_157290055.1465003565033" X-Trace: ger.gmane.org 1465003577 31654 80.91.229.3 (4 Jun 2016 01:26:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 4 Jun 2016 01:26:17 +0000 (UTC) To: ISO C++ Standard - Future Proposals Original-X-From: std-proposals+bncBCS7TY6DTQOBBLW4ZC5AKGQEALDLRJY@isocpp.org Sat Jun 04 03:26:10 2016 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-pa0-f71.google.com ([209.85.220.71]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1b90Lo-0003WW-L6 for gclcip-std-proposals@m.gmane.org; Sat, 04 Jun 2016 03:26:08 +0200 Original-Received: by mail-pa0-f71.google.com with SMTP id fg1sf117583026pad.1 for ; Fri, 03 Jun 2016 18:26:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isocpp-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=6gFIOHD9vcwwlDmgquBa9J+M8efcYJq+XestY1B+Tj8=; b=AEkuTEBUskqkcLyoGFxbgYq4H2I+uM6iRL9SBIWJU9Ai9krkewlNZ1VTTjg2BCFlY6 rOpsx4p23l11ZmnyQeL4F+9WHtuvF+Q1X9auxI9f2ooqcz0KQGEnVjMo3KuK1IQBKWFo xmW2g2MhFEPjOr0KS/JYK/jSPvUxUYxLbQSaoxDFp3b/UsAah52F/JCerRbWvAK/q7hs z0Y8vxJqYMkcDPihIcUsR0lth0b07dYHEnLzB64ItfDpoOmFi3SgdYd3uslOkfB+TT+x 8xPZLZqzTuIR9bwZiEKhkhFMSa3EgsGCHp9oya6sT8EdZgk98JgatWSZbOwxGqGyqHr+ b6CQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=6gFIOHD9vcwwlDmgquBa9J+M8efcYJq+XestY1B+Tj8=; b=vP6TWaWlEM/kP2jOVG2c1XyT2eoqDOQbtaMbVt4LUdyx5Lg2+/JgxVqaKrOAeZk6P0 tcoUouu7BawJcyZhhdrHKMjqF5do0MI6EDYXcrEWnxJ+2V0Dqiwt9fHN1475H+BuoZKR PjaTdlsXjEPAmhPFb9j7iWAMHqts8pCH/znWLFAuleHWhpHoXc6Q9OVZe/yGdRMjrsDl LQPXxYG42ku3lU5C80zCT90U4Lzf6/MJ1gNXraIsh4y0dAcjjRRu4FjH3XlExVhXO3Sl cm39AyBxrIpG2hlpjLhHd86XF2/VHZI0fqX+utFXp6NR2r3Nm/kKrpQxLsQzlkVEWgqR FUkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version:x-original-sender:reply-to:precedence :mailing-list:list-id:x-spam-checked-in-group:list-post:list-help :list-archive:list-subscribe:list-unsubscribe; bh=6gFIOHD9vcwwlDmgquBa9J+M8efcYJq+XestY1B+Tj8=; b=EVQ9fWuLp7vRcH2VbkF1Tngz5/z+eVEdVvnorVSz+i7VDMIsQNw0rULUd5kWZ+lUri M/72lCq33tqOv2fLnCgeyV9BZ+mlXygV9G6kChLPIKI99HJHYlLfa23yQc6R4v4uOlXP 53Drjr6a0MEXvhWm7pn0lCjw0FYMXnYkyHzX3ZY1VG5eF1XNh02HIGHvU7dlvIjVAfEY 3uFrysXx6DrwXhGFps8gwBkz1oyvi7kjxfLkBmVSukYR4ymB7AS9ktso2CXSYCcoHlzV 7nFJasbgM3FYWnfJqV7jOQMRJa21ZgOL25vpZRj4ShtlZZ3poEZoprOWu/Vchg28Q/uI zYYQ== X-Gm-Message-State: ALyK8tJWdWd3SFQHyd/sf8ZT5eL1Faec75c3jnQaWqPpzRtmSdiZ769i+Rb58g11zZLcMQ== X-Received: by 10.66.233.39 with SMTP id tt7mr4709198pac.29.1465003566941; Fri, 03 Jun 2016 18:26:06 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.36.76.149 with SMTP id a143ls139711itb.17.gmail; Fri, 03 Jun 2016 18:26:06 -0700 (PDT) X-Received: by 10.36.103.134 with SMTP id u128mr87047itc.5.1465003566010; Fri, 03 Jun 2016 18:26:06 -0700 (PDT) In-Reply-To: <1580229.cHEgQxCuA1@tjmaciei-mobl1> X-Original-Sender: alexander.zywicki@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:26161 Archived-At: ------=_Part_1136_157290055.1465003565033 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Friday, June 3, 2016 at 8:09:11 PM UTC-5, 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). >=20 > That I agree with. >=20 > But should the standard mandate that there should be at least one? How do= es=20 > someone write a plugin to the C++ Standard Library? Will we now mandate t= his=20 > kind of ability? >=20 > If not, then will there be a requirement that the C++ library vendor prov= ide=20 > it? If so, please think carefully how Apple should code libc++ to work on= iOS. >=20 > Again, I think this is not material for the C++ Standard Library. >=20 > --=20 > Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org > Software Architect - Intel Open Source Technology Center I do not think that this is as big as an issue as you portray it, each majo= r platform provides its own mechanism for interfacing with audio hardware. = Core Audio on OS X, Alsa on many Linux systems, etc... The standard would s= upply a specification of an interface that the compiler vendor could use to= wrap the platform specific code needed to interact with the audio hardware= .. if the target platform provides a platform specific library for audio it = should be reasonable for a compiler vendor for that platform to integrate t= hat library into its version of libc++.=20 As far as how someone would write a plugin for the std library? You can wri= te custom alligators, deleters and such, why couldn't you write a device dr= iver given a interface specification?=20 Should at least one possible driver be available? In an ideal world yes, at= minimum you should be able to load a file right? But an audio driver for t= he library? If it's available from the system, the compiler vendor would be= allowed to create a driver around that library. rather than specifying a m= inimum required number of drivers be available, why not just specify that i= n the case that your vendor does not supply one that a interface is provide= d for you to create your own. But at the same time it would not be very dif= ficult for the vendor to supply at least one for major platforms? The only = issue I could see is for an embedded system which may not run an OS? But ev= en then the developer could just create one for that target... --=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/d8b400fc-1fe2-4878-b389-abaace8818d7%40isocpp.or= g. ------=_Part_1136_157290055.1465003565033-- .