From: Scott <drmemory@3rivers.net>
To: linux-c-programming@vger.kernel.org
Subject: Re: Initializer element is not constant
Date: Fri, 21 Jan 2005 11:54:54 -0700 [thread overview]
Message-ID: <20050121185454.GB977@drmemory.local> (raw)
In-Reply-To: <41F13FF7.4020802@hq.ntsp.nec.co.jp>
On Sat, Jan 22, 2005 at 01:46:31AM +0800, Ron Michael Khu wrote:
> have u tried changing the first field of each element??
> something like... replacing those char ptrs with something static?
>
> example:
>
> DATUM recip_data[] = {
> { "i am a constant str", NAMECTRL_LEN, make_upper },
> { "i am a constant str", NAME1_LEN, make_upper },
As I recalled, the ability to HAVE dynamic pointers was one of the
primary benefits of using c in the first place! Later in the file I
have this routine which allocates space for each pointer in the
structure:
alloc_space(r) RECORD *r;
{ register size_t i;
register char **v;
for(i=0; i<r->n; i++)
{ if(r->data[i].len == 0 || r->data[i].len == 0xFFFF) continue;
v = (r->data[i].var);
if (*v == NULL)
{ *v = (char *) calloc(1,r->data[i].len + 1);
memset(*v,'A'+i,r->data[i].len);
}
}
}
I guess i just don't understand why a "modern" compiler wants to
restrict my options in this fashion....
next prev parent reply other threads:[~2005-01-21 18:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 23:21 Initializer element is not constant Scott
[not found] ` <41F06AC1.2000605@hq.ntsp.nec.co.jp>
2005-01-21 2:37 ` Ron Michael Khu
2005-01-21 16:27 ` Scott
2005-01-21 17:46 ` Ron Michael Khu
2005-01-21 18:54 ` Scott [this message]
2005-01-21 19:50 ` Ron Michael Khu
2005-01-21 21:31 ` Scott
2005-01-22 21:12 ` Christoph Bussenius
2005-01-24 20:44 ` Scott
-- strict thread matches above, loose matches on Subject: below --
2005-01-24 21:09 Huber, George K RDECOM CERDEC STCD SRI
2005-01-24 21:28 ` Scott
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=20050121185454.GB977@drmemory.local \
--to=drmemory@3rivers.net \
--cc=linux-c-programming@vger.kernel.org \
/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).