From: "Ville Syrjälä" <syrjala@sci.fi>
To: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Re: Memory managment.
Date: Tue, 7 May 2002 05:18:37 +0300 [thread overview]
Message-ID: <20020507051837.A5750@sci.fi> (raw)
In-Reply-To: <s5hk7qhmuja.wl@alsa2.suse.de>; from tiwai@suse.de on Mon, May 06, 2002 at 12:37:29PM +0200
On Mon, May 06, 2002 at 12:37:29PM +0200, Takashi Iwai wrote:
> snd_seq_event_output() copies the event instance, so a temporary
> variable can be used safely in the above.
What about snd_seq_event_input()? The comments in the code suggest that it
uses snd_seq_event_create() but I don't see it. It doesn't seem to
allocate anything. Do I have to supply it with a pointer to a preallocated
event structure? If that's the case the example code in the alsa-lib/test
directory is broken. Actually it's broken in either case since
like you said snd_seq_free_event() doesn't free anything.
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
next prev parent reply other threads:[~2002-05-07 2:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-05 17:35 Memory managment Peter Enderborg
2002-05-06 9:42 ` Takashi Iwai
2002-05-06 10:09 ` Peter Enderborg
2002-05-06 10:37 ` Takashi Iwai
2002-05-06 11:01 ` Peter Enderborg
2002-05-07 2:18 ` Ville Syrjälä [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-05 14:27 Peter Enderborg
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=20020507051837.A5750@sci.fi \
--to=syrjala@sci.fi \
--cc=alsa-devel@lists.sourceforge.net \
/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.