what is 0xFFFFFFF ?

[iskeletor]

in a program it is passing like that:

#define INFINITY 0xFFFFFFF

it is a ASCII code of what? or is it a address that a pointer hold?
so adress of what?

[Chris Dollin]

iskeletor wrote:

in a program it is passing like that:

#define INFINITY 0xFFFFFFF

it is a ASCII code of what? or is it a address that a pointer hold?
so adress of what?

It's a biggish [1] number, that's all.

[1] From the point of view of 32-bit machine integers in twos complement.
From any reasonable point of view, it's a peanut: not even 2pow32,
let alone (searches for a number) 10pow100.

--
Chris "electric hedgehog" Dollin
"It took a very long time, much longer than the most generous estimates."
- James White, /Sector General/

[=?utf-8?B?SGFyYWxkIHZhbiBExLNr?=]

iskeletor wrote:

in a program it is passing like that:

#define INFINITY 0xFFFFFFF

it is a ASCII code of what? or is it a address that a pointer hold?
so adress of what?

0xFFFFFFFF is a hexadecimal integer constant. Its decimal value is
simply 4294967295. As far as C is concerned, that does not mean
infinity. Applications, however, may choose to have it mean exactly
that, just as they may choose 2 to mean infinity.

I don't know if you know what hexadecimal means. If you don't, a quick
search gives me
http://www.pcnineoneone.com/howto/hex1.html
as one possible introduction.

[Lew Pitcher]

On Jan 24, 9:43 am, "iskeletor" <zirvedo...@gma il.comwrote:

in a program it is passing like that:

#define INFINITY 0xFFFFFFF

it is a ASCII code of what?

Nope. It isn't ASCII

or is it a address that a pointer hold?
so adress of what?

It is unlikely that it is a pointer

Technically

#define INFINITY 0xFFFFFFF

tells the compiler to replace the token INFINITY with the token
0xFFFFFFF whenever the compiler encounters it in the source code. The
context of the source code statement that uses this INFINITY /
0xFFFFFFF token will give you "what it is".

0xFFFFFFF is taken as an integer value

It /might/ be used as the initializer for a pointer
It /might/ be used as the initializer for an integer data item

It depends on the context

HTH
--
Lew

[iskeletor]

I don't know if you know what hexadecimal means. If you don't, a quick
search gives me
http://www.pcnineoneone.com/howto/hex1.html
as one possible introduction.

thanx i know hexadecimal.I understood =))

[Matthew Hicks]

Or it's a small negative number, -1. It's only a big positive number (what
it is supposed to represent given the context) if the system/program uses
32-bit unsigned ints.
---Matthew Hicks

iskeletor wrote:

>in a program it is passing like that:

#define INFINITY 0xFFFFFFF

it is a ASCII code of what? or is it a address that a pointer hold?
so adress of what?

It's a biggish [1] number, that's all.

[1] From the point of view of 32-bit machine integers in twos
complement.
From any reasonable point of view, it's a peanut: not even 2pow32,
let alone (searches for a number) 10pow100.

[Chris Dollin]

Harald van Dijk wrote:

iskeletor wrote:

>in a program it is passing like that:

#define INFINITY 0xFFFFFFF

it is a ASCII code of what? or is it a address that a pointer hold?
so adress of what?

0xFFFFFFFF is a hexadecimal integer constant.

Nitpick: the OP's text said 0xFFFFFFF, not 0xFFFFFFFF.
(One difference is that on a 32-bit-int implementation,
the OP's text will become a signed int literal but
yours will become an /unsigned/ int literal. If I
remember correctly.)

--
Chris "integral hedgehog" Dollin
"Who are you? What do you want?" /Babylon 5/

[Richard Tobin]

In article <11************ *********@h3g20 00cwc.googlegro ups.com>,
Harald van Dijk <tr*****@gmail. comwrote:

>#define INFINITY 0xFFFFFFF

>0xFFFFFFFF is a hexadecimal integer constant. Its decimal value is
simply 4294967295.

The number was 0xFFFFFFF, not 0xFFFFFFFF. The latter might be a bad
choice as a large number on many current machines, since it would be
-1 if stored in an int. INT_MAX would be more portable.

-- Richard
--
"Considerat ion shall be given to the need for as many as 32 characters
in some alphabets" - X3.4, 1963.

[Chris Dollin]

Matthew Hicks wrote:

Please don't top-post. Thanks. Fixed.

>iskeletor wrote:

>>in a program it is passing like that:

#define INFINITY 0xFFFFFFF

it is a ASCII code of what? or is it a address that a pointer hold?
so adress of what?

It's a biggish [1] number, that's all.

[1] From the point of view of 32-bit machine integers in twos
complement.
From any reasonable point of view, it's a peanut: not even 2pow32,
let alone (searches for a number) 10pow100.

Or it's a small negative number, -1. It's only a big positive number (what
it is supposed to represent given the context) if the system/program uses
32-bit unsigned ints.

Count Fs.

It's positive anyway: if the value /was/ 0xFFFFFFFF, then on a 32-bit
implementation it will be an unsigned int, not a signed int. IIRC.

--
Chris "electric hedgehog" Dollin
"- born in the lab under strict supervision -", - Magenta, /Genetesis/

[Matthew Hicks]

Ignore my previous post as Mr. Tobin pointed out that there are only 7 hex
characters. On a side note, 0x7fffffff would probably be a better general
coice for infinity on most 32-bit machines.
---Matthew Hicks

Or it's a small negative number, -1. It's only a big positive number
(what it is supposed to represent given the context) if the
system/program uses 32-bit unsigned ints.

---Matthew Hicks

>iskeletor wrote:

>>in a program it is passing like that:

#define INFINITY 0xFFFFFFF

it is a ASCII code of what? or is it a address that a pointer hold?
so adress of what?

It's a biggish [1] number, that's all.

[1] From the point of view of 32-bit machine integers in twos
complement.
From any reasonable point of view, it's a peanut: not even 2pow32,
let alone (searches for a number) 10pow100.