From: Micha Feigin <michf@post.tau.ac.il>
To: linux-c-programming@vger.kernel.org
Subject: Re: Fwd: constant in C
Date: Fri, 24 Sep 2004 12:17:18 +0200 [thread overview]
Message-ID: <20040924101717.GC9014@luna.mooo.com> (raw)
In-Reply-To: <4f2e7cd304092400333259f597@mail.gmail.com>
On Fri, Sep 24, 2004 at 01:03:17PM +0530, Uday Karan wrote:
> Sorry didn't CC to list.
>
> > Therefore you cannot use sizeof(const), &const etc.
>
> sizeof (CONST) can be done and would return the size of an integral
> type that would be able to hold that value, could be 4 for ints or 8
> for long ints, if none of these can take up the value (because you're
Actually the size of long int is 4 and the size of short is 2, the size
of int depends on the platform. With the old 16bit platforms (if you
can still find them ;-) it was 2 and with 32 bit machines its 4.
Int was supposed to be a word, but on 64bit machines that is not longer
stable.
with 64bits, a pointer is of size 8, but int and long can be either 4
or 8 and sometimes there is long long.
have look at http://en.wikipedia.org/wiki/64-bit.
> substitutive constant is insanely large), the compiler would usually
> give out a warning (if truncating) or an error straightaway.
>
> - Uday
> -
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> +++++++++++++++++++++++++++++++++++++++++++
> This Mail Was Scanned By Mail-seCure System
> at the Tel-Aviv University CC.
>
next prev parent reply other threads:[~2004-09-24 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 3:36 constant in C Ankit Jain
2004-09-24 7:16 ` Andrei Bunghez
[not found] ` <4f2e7cd304092400315c83fd1e@mail.gmail.com>
2004-09-24 7:33 ` Fwd: " Uday Karan
2004-09-24 10:17 ` Micha Feigin [this message]
2004-09-24 10:47 ` Ankit Jain
2004-09-25 0:53 ` Micha Feigin
2004-09-24 7:18 ` Andrei Bunghez
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=20040924101717.GC9014@luna.mooo.com \
--to=michf@post.tau.ac.il \
--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).