From: Randi Botse <nightdecoder@gmail.com>
To: Michal Nazarewicz <mina86@tlen.pl>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: C Question
Date: Tue, 1 Jun 2010 07:59:37 -0400 [thread overview]
Message-ID: <AANLkTik-eE99MeOMhJKcINHwzyzT_BcduarrMLVWvCDs@mail.gmail.com> (raw)
In-Reply-To: <87r5ktfttj.fsf@erwin.mina86.com>
That's clear now, i was though the 'unindexed' strings (in this case
index 1, 2, 3, and 5) remains unintialized (not initialized to NULL).
Thanks very much.
Randi,
2010/5/30 Michal Nazarewicz <mina86@tlen.pl>:
> Randi Botse <nightdecoder@gmail.com> writes:
>> Yes, the N_(x) macro used for localization that i discard in my question.
>>
>> Sorry but, i just having another question, consider this code:
>>
>> const char *my_strings[] = {
>> [0] = "index0",
>> [4] = "index4",
>> [6] = "index6"
>> };
>
> NULLs will be written at indexes 1, 2, 3 and 5. There will be total of
> 7 pointers (the last one will point to "index6").
>
> --
> Best regards, _ _
> .o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o
> ..o | Computer Science, Michal "mina86" Nazarewicz (o o)
> ooo +--<mina86-tlen.pl>--<jid:mina86-jabber.org>--ooO--(_)--Ooo--
>
--
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-01 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 10:08 C Question Randi Botse
2010-05-25 10:19 ` Xiaotian Feng
[not found] ` <AANLkTinTu94E7guvzjySpGjht2Hjw4aop4vRIVpHo9UL@mail.gmail.com>
2010-05-25 10:49 ` Randi Botse
2010-05-25 11:18 ` Uriel Corfa
2010-05-25 11:41 ` Michal Nazarewicz
2010-05-30 10:41 ` Randi Botse
2010-05-30 12:38 ` Michal Nazarewicz
2010-06-01 11:59 ` Randi Botse [this message]
2010-06-01 13:18 ` Glynn Clements
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=AANLkTik-eE99MeOMhJKcINHwzyzT_BcduarrMLVWvCDs@mail.gmail.com \
--to=nightdecoder@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=mina86@tlen.pl \
/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;
as well as URLs for NNTP newsgroup(s).