Search found 27 matches

Add one more comment to this thread.
In CCS C (for the PIC 12/16/18), the format of FP numbers in memory, is different from the IEEE format used inside a PC.
The file 'ieeefloat.c', contains two rou ...

In addition I will show how float is stored. It is stored with 32 bits in memory.

Now look at my demonstration below

Example 1

int buff[10];

int32 *fp;
float F =123.45;
fp = &F;
i ...

What is wrong with the obvious:

long L;
float F = 12345.6;

L = F;

Should leave L = 12345

int16 i;

Cast it

i=(int16)F;

Octal representation begins with a 0 not an O

True. Thanks

A Typo I tested it with 0 not O. I have corrected listing above

compiler version PCH 4.104

You might look at this ccs thread and ask many questions

https://www.ccsinfo.com/forum/viewtopic.php?t=23400

Now I will show some interesting enum statements that compile with ccs.

1. ...

You might look at this ccs thread and ask many questions

https://www.ccsinfo.com/forum/viewtopic.php?t=23400

Now I will show some interesting enum statements that compile with ccs.

1. enum{u, ...

But this thread is about the line:-

#define test 0x42

Either, the poster doesn't know much about C so describing the ins and outs of lvalues and const's isn't going to help or John P post is co ...

Non-modifiable lvalues vs. rvalues (see below for defination)

The crux of the problem with constant objects is that, while an enumeration constant is an rvalue, a constant object is a non-modifiabl ...

Using const and rom takes up space and can add extra processing

"const" construct, on the other hand, does all the type checking that the compiler does, so if you do something that's out ...

What does it mean this line? 0x42?

#define test 0x42

Tks a lot

Nina Pretty Ballerina,

My preferred way of doing things when dealing with values or numbers or instead of always using th ...

hello.
what i don't right do

CONST char TEXT_KSW[]="ÊÑÂ";
CONST char TEXT_POWER[]="ÌÎÙÍÎÑÒÜ";
CONST char TEXT_P_KONTUR[]="Ï-ÊÎÍ ...

edit - I just noticed your last statement. Why do you think a rom pointer for a PIC18F8722 is 4 bytes ?

I do not think it is 4 bytes. I know it is 4 bytes because the program space is 128K bytes. ...

....

I would do it differently and report a problem to CCS.

well it should report 16/4 =4. Dont you think so?

sizeof(strings) = 16;
sizeof(rom char*) = 4;

My device is PIC18F8722 so the ...

Well, my compiler works differently to yours.

Or did you work it out some other way ?

So whose compiler is doing the right thing?