All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Koenig <mkoenig@suse.de>
To: haoshun <haoshun@amoi.com.cn>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: Problems in writing test apps
Date: Thu, 03 Apr 2008 11:59:00 +0200	[thread overview]
Message-ID: <n7xmyobi7iz.fsf@sor.suse.de> (raw)
In-Reply-To: <200804031659332034329@amoi.com.cn> (haoshun@amoi.com.cn's message of "Thu\, 3 Apr 2008 16\:59\:33 +0800")

"haoshun" <haoshun@amoi.com.cn> writes:

> Hi:
>       sorry,forget to add the subject right now...
>       I'm confused by a problem when i modify a test application
>       "alsa-lib-1.0.13/test/control.c".  I wanna use the structure
>       "snd_ctl_elem_value_t",but when i write like this:
>              snd_ctl_elem_value_t aaa;
>       there will be an error:
>              storage size of 'aaa' isn't known
>      while 
>              snd_ctl_elem_value_t *aaa;
>      makes no errors. But i can't change it directly such as:
>              aaa->id=test_id ; //test_id is defined before
>      cause it will bring an error:
>              dereferencing pointer to incomplete type
>      I think i should use the function like
>      "snd_ctl_elem_info_set_id",but i just want to know why,i don't
>      think it disobeys the C syntax.Is there something different in
>      the ALSA making procedure?or Makefile?

The ALSA data types are designed to be opaque. You cannot access the 
members of the structures directly as the structure definitions are 
simply not exported on purpose.  You have to use the access functions.
E.g. allocating a snd_ctl_elem_value_t structure will be done with the
int snd_ctl_elem_value_malloc(snd_ctl_elem_value_t **ptr)

Matthias

      reply	other threads:[~2008-04-03  9:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03  8:59 Problems in writing test apps haoshun
2008-04-03  9:59 ` Matthias Koenig [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=n7xmyobi7iz.fsf@sor.suse.de \
    --to=mkoenig@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=haoshun@amoi.com.cn \
    /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.