From: arijitg@uci.edu
To: <gcc-help@gcc.gnu.org>
Subject: Re: Bamboozled by long long
Date: Fri, 19 Jul 2002 13:11:00 -0000 [thread overview]
Message-ID: <1027109514.smmsdV1.1.2@smtp.uci.edu> (raw)
I tried running it on my system with both options.
llx works while LX does not.
My system is sunOS5.7 just in case.
thanks guys for the prompt and right response. :)
---------Included Message----------
>Date: Fri, 19 Jul 2002 12:31:23 -0700
>From: "Gokhan Kisacikoglu" <kisa@centropolisfx.com>
>Reply-To: <kisa@centropolisfx.com>
>To: "John Love-Jensen" <eljay@adobe.com>
>Cc: <arijitg@uci.edu>, <gcc-help@gcc.gnu.org>
>Subject: Re: Bamboozled by long long
>
>
>> unsigned long long k=1;
>> unsigned int i = 4;
>> printf("The values are i: %d, , k: %LX, i+k: %LX \n", i,k , i+k);
>> k = k + i;
>> printf("The values are i: %d, , k: %LX, i+k: %LX \n", i,k , i+k);
>>
>> ...depending on the extension (or convention for long long) used.
>>
>> --Eljay
>
>
>This is not correct, this will only work with double precision float
>numbers. "long long" is really "long long int" and only ll should be
>used. This is from the man page (on my system):
>
> ll For n, the argument has type pointer to long long int;
for
>d
> and i, long long int; and for o, u, x, and X, unsigned
long
> long int.
>
> L For b, B, e, E, f, g, and G, the argument has type long
> double.
>
>
---------End of Included Message----------
next reply other threads:[~2002-07-19 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 13:11 arijitg [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-19 11:17 arijitg
2002-07-19 12:16 ` John Love-Jensen
2002-07-19 12:29 ` Gokhan Kisacikoglu
2002-07-19 14:22 ` Leo Przybylski
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=1027109514.smmsdV1.1.2@smtp.uci.edu \
--to=arijitg@uci.edu \
--cc=gcc-help@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).