linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mohammed Khalid Ansari <khalid@ncst.ernet.in>
To: linux c programming mailing list <linux-c-programming@vger.kernel.org>
Subject: problem with const in structure
Date: Mon, 6 Jan 2003 18:53:15 +0530 (IST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0301061759250.14169-100000@soochak.ncst.ernet.in> (raw)


Hi,

consider the following code.

####
#include <stdio.h>

struct node {
	const int x;
	char name[20];
	struct node *next;
};

int main()
{
	struct node newnode;
		
	newnode.x = 10;
	newnode.x = 12;
	printf ("x = %d\n", newnode.x);
	return 0;
}
####

Now, you can see that even though I have defined x to be const int, I can 
assign it values. When I compiled the program, it gives the warning that 
assignment of read-only member x but when I ran the program, it worked 
fine. Where is the catch. How do I define a structure variable to be 
const?

with regards...

-- 

**************************************************************************

Mohammed Khalid Ansari                    Tel (res) : 0091-022-3051360
Assistant Manager II                          (off) : 0091-022-2024641
National Centre for Software Technology   Fax       : 0091-022-2049573 
8th flr,Air India Build. Nariman Point,   E-Mail    : khalid@ncst.ernet.in 	
Mumbai 400021.

Homepage : http://soochak.ncst.ernet.in/~khalid			  	  

**************************************************************************



             reply	other threads:[~2003-01-06 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-06 13:23 Mohammed Khalid Ansari [this message]
2003-01-06 15:48 ` problem with const in structure Glynn Clements
  -- strict thread matches above, loose matches on Subject: below --
2003-01-06 17:46 

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=Pine.LNX.4.33.0301061759250.14169-100000@soochak.ncst.ernet.in \
    --to=khalid@ncst.ernet.in \
    --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).