Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8940369
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 15, 20262026-06-15T11:01:11+00:00 2026-06-15T11:01:11+00:00

Are struct well defined in strict c 89? I mean this code struct a

  • 0

Are struct well defined in strict c 89?
I mean this code

struct a {
    int a, b;
    void * c;
} k;
//init k...
struct b {
    int u, w;
    long *data;
} p = *(struct b*)&k;

is going to work on every compiler that support the standard? If I reverse the cast (e.g. cast from struct b to struct a) c is going to be the same as the beginning?
I’m pretty sure it works with gcc(even with -ansi -pedantic), microsoft compiler and so on, but does it guarantee that it is standard c 89?

Thank you!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-15T11:01:13+00:00Added an answer on June 15, 2026 at 11:01 am

    Don’t do this. Copy the fields manually:

    struct b p;
    
    p.u = k.a;
    p.w = k.b;
    p.data = (long *) k.c;
    

    Your code would most likely run just fine since long * and void * will typically be identically implemented, but why risk it? The standard says stuff like:

    A pointer to void shall have the same representation and alignment requirements as a
    pointer to a character type.39) Similarly, pointers to qualified or unqualified versions of
    compatible types shall have the same representation and alignment requirements. All
    pointers to structure types shall have the same representation and alignment requirements
    as each other. All pointers to union types shall have the same representation and
    alignment requirements as each other. Pointers to other types need not have the same representation or alignment requirements.

    Note the last sentence, where pointers to “other types” (such as long) are made distinct from pointers to void.

    The above is explicit, safe, and much clearer.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

struct Foo { int data; Foo() = default; Foo(const Foo& arg) = default; };
Is this program well-defined, and if not, why exactly? #include <iostream> #include <new> struct
struct SomeStruct { int a; int b; }; SomeStruct someFn( int init ) {
struct Div { int i; int j; }; class A { public: A(); Div&
I have a structure defined like so: typedef struct { int n; int *n_p;
I wonder if construction like this (initialization list) has well defined EO (evaluation order):
I am having a struct defined in C++ which contains int and std::string arrays
Is the a amount of padding in C struct well defined in standards or
Suppose there is CGo package with a struct defined like this: package test ...
struct pointsto_val_def { unsigned int lhs; bitmap rhs; struct pointsto_val_def *next; }; typedef struct

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.