All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: hamren@sdu.se, alsa-devel@lists.sourceforge.net
Subject: Re: Re: Extended API: Constructors and alloca()
Date: Fri, 21 Mar 2003 14:14:56 +0100	[thread overview]
Message-ID: <s5h8yv8rhdb.wl@alsa2.suse.de> (raw)
In-Reply-To: <E18wLwB-0001c4-00@sc8-sf-list1.sourceforge.net>

At Fri, 21 Mar 2003 07:51:41 -0500,
Paul Davis wrote:
> 
> >> It would be a good thing if the necesary structs (snd_ctl_t, et c.)
> >> were available in an unofficial include file in the library.
> >
> >THIS is the very question.
> >so far, in the implementation of alsa-lib, we have been trying to hide
> >this.  the all strucs are suppose to be opaque (except for some
> >trivial cases).
> >putting the struct in public (even though it's unofficial) breaks this
> >policy.
> 
> i (and i hope many other ALSA users/developers) would scream very
> loudly if we moved from this design/policy. it has been critical and
> central to success in stabilizing the API from the perspective of
> applications. it has worked for Xlib for a long time, it has worked
> for us for a year or more, and we should not change this. making the
> change proposed by lars would open us up to major binary compatibility
> issues as alsa evolves.

agreed, the compatibility must be kept.

as mentioned in the last mail, our initial plan is to make a c++
library which covers the existing alsa-lib, that is, alsa-lib++.

alsa-lib API (in C) won't be changed by this, i promise you.


Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      reply	other threads:[~2003-03-21 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15994.3590.553705.504916@maxi.int.sdu.se>
2003-03-21 11:12 ` Extended API: Constructors and alloca() Takashi Iwai
2003-03-21 12:51   ` Paul Davis
2003-03-21 13:14     ` Takashi Iwai [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5h8yv8rhdb.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=hamren@sdu.se \
    --cc=paul@linuxaudiosystems.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.