enum as return type

[Felix Kater]

Hi,

is it valid to declare the variable 'e' of type 'my_enum' to later hold
the return value of function f2 -- or must e by of type int?

Felix

typedef enum{
a_my_enum,
b_my_enum,
c_my_enum
}my_enum;

my_enum f2(void){
return a_my_enum;
}

void f(void){
my_enum e; /* ok? or must e by of type int? */
e=f2();
}

[Eric Sosman]

Felix Kater wrote:

Hi,

is it valid to declare the variable 'e' of type 'my_enum' to later hold
the return value of function f2 -- or must e by of type int?

Felix

typedef enum{
a_my_enum,
b_my_enum,
c_my_enum
}my_enum;

my_enum f2(void){
return a_my_enum;
}

void f(void){
my_enum e; /* ok? or must e by of type int? */
e=f2();
}

OK.

--
Eric Sosman
es*****@acm-dot-org.invalid

[Barry]

"Felix Kater" <fk****@googlemail.comwrote in message
news:20****************************@googlemail.com ...

Hi,

is it valid to declare the variable 'e' of type 'my_enum' to later hold
the return value of function f2 -- or must e by of type int?

Felix

typedef enum{
a_my_enum,
b_my_enum,
c_my_enum
}my_enum;

my_enum f2(void){
return a_my_enum;
}

void f(void){
my_enum e; /* ok? or must e by of type int? */
e=f2();
}

Why didn't you just add:

int main(void)
{
return 0;
}

and try it?

[Richard Heathfield]

Barry said:

"Felix Kater" <fk****@googlemail.comwrote in message
news:20****************************@googlemail.com ...

>is it valid to declare the variable 'e' of type 'my_enum' to later hold
the return value of function f2 -- or must e by of type int?

<snip>

>
Why didn't you just add:

int main(void)
{
return 0;
}

and try it?

Because he wants to know whether it's valid C. Experimentation would only
give him empirical data, not proof of validity.
--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999
http://www.cpax.org.uk
email: rjh at the above domain, - www.

[CBFalconer]

Barry wrote:

"Felix Kater" <fk****@googlemail.comwrote in message

>>
is it valid to declare the variable 'e' of type 'my_enum' to later hold
the return value of function f2 -- or must e by of type int?

typedef enum{
a_my_enum,
b_my_enum,
c_my_enum
}my_enum;

my_enum f2(void){
return a_my_enum;
}

void f(void){
my_enum e; /* ok? or must e by of type int? */
e=f2();
}

Why didn't you just add:

int main(void)
{
return 0;
}

and try it?

Because that doesn't answer the generic validity question.

--
Chuck F (cbfalconer at maineline dot net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net>

[Keith Thompson]

Felix Kater <fk****@googlemail.comwrites:

is it valid to declare the variable 'e' of type 'my_enum' to later hold
the return value of function f2 -- or must e by of type int?

Felix

typedef enum{
a_my_enum,
b_my_enum,
c_my_enum
}my_enum;

my_enum f2(void){
return a_my_enum;
}

void f(void){
my_enum e; /* ok? or must e by of type int? */
e=f2();
}

Yes, that's fine, and clearer than declaring e to be of type int.
Integer types and enum types can be freely assigned to each other.
In fact, enum constants (a_my_enum et al) are actually of type int.

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <* <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.