Connecting Tech Pros Worldwide Help | Site Map

initialize static structured variable challenge

 
LinkBack Thread Tools Search this Thread
  #1  
Old July 22nd, 2005, 02:05 PM
wim delvaux
Guest
 
Posts: n/a
Default initialize static structured variable challenge

Hi all,

I want to initialize two structures with pointers
to eachother

static StructA VarA = { PtrToVarB };
static StructB VarB = { PtrToVarA };

A solution that WORKS in C (using gcc 3.3) is

static StructA VarA; // defining VarA
static StructB VarB; // defining VarB

and then

static StructA VarA = { &VarB };
static StructB VarB = { &VarA };

However in C++ (same gcc version) it does not work because
the first static is not assumed to be tentative.

How can I solve this problem ? Initializing using
functions is not possible since the above code is
generated automatically by some compiler

W



  #2  
Old July 22nd, 2005, 02:06 PM
Gianni Mariani
Guest
 
Posts: n/a
Default Re: initialize static structured variable challenge

wim delvaux wrote:[color=blue]
> Hi all,
>
> I want to initialize two structures with pointers
> to eachother
>
> static StructA VarA = { PtrToVarB };
> static StructB VarB = { PtrToVarA };
>
> A solution that WORKS in C (using gcc 3.3) is
>
> static StructA VarA; // defining VarA
> static StructB VarB; // defining VarB
>
> and then
>
> static StructA VarA = { &VarB };
> static StructB VarB = { &VarA };
>
> However in C++ (same gcc version) it does not work because
> the first static is not assumed to be tentative.
>
> How can I solve this problem ? Initializing using
> functions is not possible since the above code is
> generated automatically by some compiler[/color]

namespace
{
extern StructA VarA;
extern StructB VarB;

StructA VarA = { &VarB };
StructB VarB = { &VarA };
};

I didn't test it, but the above should compile. Note that the "extern"
in an anonymous namespace has about the same meaning as static.
  #3  
Old July 22nd, 2005, 02:06 PM
wim delvaux
Guest
 
Posts: n/a
Default Re: initialize static structured variable challenge

namespace {
typedef struct x_s {
int x;
} x_t;

extern x_t X1;
extern x_t X2;

static x_t X1 = { &X2 };
static x_t X2 = { &X1 };
}

Compiled above code ...

u19809@buro:.../tmp$ c++ --version
c++ (GCC) 3.3.3 (Debian 20040417)
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Result :

u19809@buro:.../tmp$ c++ t.c -o t++
t.c:9: error: `<unnamed>::X1' was declared `extern' and later `static'
t.c:6: error: previous declaration of `<unnamed>::X1'
t.c:9: error: invalid conversion from `<unnamed>::x_t*' to `int'
t.c:10: error: `<unnamed>::X2' was declared `extern' and later `static'
t.c:7: error: previous declaration of `<unnamed>::X2'
t.c:10: error: invalid conversion from `<unnamed>::x_t*' to `int'



  #4  
Old July 22nd, 2005, 02:06 PM
Buster
Guest
 
Posts: n/a
Default Re: initialize static structured variable challenge

wim delvaux wrote:

What you tried is totally different from what Gianni suggested.
The 'static' keyword has managed to sneak back in. I compiled
the following, as a complete translation unit. There were no
errors on GCC 3.3.1, MSVC 7.1 or BCB 6.0.

namespace
{
struct StructB;
struct StructA { StructB * p; };
struct StructB { StructA * p; };

extern StructA VarA;
extern StructB VarB;

StructA VarA = { &VarB };
StructB VarB = { &VarA };
};

void f()
{
StructA a;
StructB b;
}

--
Regards,
Buster.
  #5  
Old July 22nd, 2005, 03:15 PM
wim delvaux
Guest
 
Posts: n/a
Default Re: initialize static structured variable challenge

Ah ok,

one thing I am afraid of is that VarA and VarB should remain local
variables (i.e. not cause nameclashes in other modules).

Does the use of the anonymous namespace imply that the vars are hidden for
all other source files ?

W
  #6  
Old July 22nd, 2005, 03:15 PM
Gianni Mariani
Guest
 
Posts: n/a
Default Re: initialize static structured variable challenge

wim delvaux wrote:[color=blue]
> Ah ok,
>
> one thing I am afraid of is that VarA and VarB should remain local
> variables (i.e. not cause nameclashes in other modules).
>
> Does the use of the anonymous namespace imply that the vars are hidden for
> all other source files ?[/color]

yes - (modulo compiler bugs).
 

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Popular Articles

What is Bytes?

We are a network of experts and professionals in IT and software development that help one another with answers to tough questions and share insights. Get the best answers to your questions from over 220,840 network members.