On 19 December 2016 at 12:51, Masahiro Yamada
wrote:
> In the MMC subsystem, we see such initializers that only clears the
> first member explicitly.
>
> For example,
>
> struct mmc_request mrq = {NULL};
>
> sets the first member (.sbc) to NULL explicitly.
On 19 December 2016 at 12:51, Masahiro Yamada
wrote:
> In the MMC subsystem, we see such initializers that only clears the
> first member explicitly.
>
> For example,
>
> struct mmc_request mrq = {NULL};
>
> sets the first member (.sbc) to NULL explicitly. However, this is
> an unstable form
On Mon, Dec 19, 2016 at 12:51 PM, Masahiro Yamada
wrote:
> In the MMC subsystem, we see such initializers that only clears the
> first member explicitly.
>
> For example,
>
> struct mmc_request mrq = {NULL};
>
> sets the first member (.sbc) to NULL explicitly.
On Mon, Dec 19, 2016 at 12:51 PM, Masahiro Yamada
wrote:
> In the MMC subsystem, we see such initializers that only clears the
> first member explicitly.
>
> For example,
>
> struct mmc_request mrq = {NULL};
>
> sets the first member (.sbc) to NULL explicitly. However, this is
> an unstable
In the MMC subsystem, we see such initializers that only clears the
first member explicitly.
For example,
struct mmc_request mrq = {NULL};
sets the first member (.sbc) to NULL explicitly. However, this is
an unstable form because we may insert a non-pointer member at the
top of the struct
In the MMC subsystem, we see such initializers that only clears the
first member explicitly.
For example,
struct mmc_request mrq = {NULL};
sets the first member (.sbc) to NULL explicitly. However, this is
an unstable form because we may insert a non-pointer member at the
top of the struct
6 matches
Mail list logo