Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: Re: Pull request for alsa-plugins
Date: Thu, 04 Sep 2008 11:23:09 +0100	[thread overview]
Message-ID: <g9ocud$jjq$2@ger.gmane.org> (raw)
In-Reply-To: <s5h63pcnygu.wl%tiwai@suse.de>

Takashi Iwai wrote:
> One of my concerns in the current pulse code is the many use of
> assert().  In many cases, assert() is a wrong choice.  For example,
> checking the return value of malloc in assert() is definitely wrong.
> It should be always checked, and should return an error instead of
> aborting the program.
> 
> Yes, alsa-lib has also many assert() although I removed already many.
> Some of them may be still wrong ones.  Hopefully this can be sorted
> out later.

There has been a rather large thread on this on PA mailing list over the 
last couple days :)

http://thread.gmane.org/gmane.comp.audio.pulseaudio.general/2014

I personally got some stuff wrong, but learned from Lennart's responses.

Certainly I think a lot of the cases where this plugin could have 
previously hit an assert have now been removed. Not sure about the 
malloc asserts() tho'...

Col

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
   Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
   Mandriva Linux Contributor [http://www.mandriva.com/]
   PulseAudio Hacker [http://www.pulseaudio.org/]
   Trac Hacker [http://trac.edgewall.org/]

  reply	other threads:[~2008-09-04 10:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 19:17 Pull request for alsa-plugins Lennart Poettering
2008-09-04  7:48 ` Takashi Iwai
2008-09-04 10:23   ` Colin Guthrie [this message]
2008-09-04 14:03   ` Lennart Poettering

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='g9ocud$jjq$2@ger.gmane.org' \
    --to=gmane@colin.guthr.ie \
    --cc=alsa-devel@alsa-project.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox