From: Steve deRosier <derosier@pianodisc.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: Re: usage of snd_seq_queue_status_get_real_time()
Date: Fri, 08 Apr 2005 08:47:59 -0700 [thread overview]
Message-ID: <4256A7AF.6010607@pianodisc.com> (raw)
In-Reply-To: <Pine.HPX.4.33n.0504080853540.3042-100000@studcom.urz.uni-halle.de>
Good point, I should check ..._get_queue_status() for an error return. The docs don't specify any error return for ..._get_real_time() however.
I figured that it returns a pointer to a local var considering the const in the return type, but that still doesn't explain why the data never changes.
- Steve
Clemens Ladisch wrote:
> Steve deRosier wrote:
>
>>const snd_seq_real_time_t * CMIDIPort::GetRealQueueTime( void )
>>{
>> snd_seq_queue_status_t * qs;
>>
>> snd_seq_queue_status_alloca( &qs );
>> snd_seq_get_queue_status( hSeq, mQueue, qs );
>> return snd_seq_queue_status_get_real_time( qs );
>>}
>
>
> This function returns a pointer to a local variable.
>
> (And it should check for errors.)
>
>
> HTH
> Clemens
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-04-08 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 0:51 usage of snd_seq_queue_status_get_real_time() Steve deRosier
2005-04-08 6:54 ` Clemens Ladisch
2005-04-08 15:47 ` Steve deRosier [this message]
2005-04-11 8:47 ` Clemens Ladisch
2005-04-12 19:15 ` Steve deRosier
2005-04-13 8:10 ` Clemens Ladisch
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=4256A7AF.6010607@pianodisc.com \
--to=derosier@pianodisc.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
/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