Search found 8 matches

This is a cheek, to sell a compiler that does'nt work. It is intentional deception. They must have known that it does'nt work. Its not only a bug, which no one knows at the time they began to sell.

How bad, I always work with ROM Pointers. Now it's very awkward to do this stuff.

Did I understand anything wrong or should it be possible to get a pointer to ROM with 4.xx?

I tried this:

const char status_g_2_blink[12] = {"G__G_______"};
const c ...

Hi,

some questions: Do I have to use the PGM-Pin (Low voltage Programming) on PIC18 devices, when I want to use a Bootloader? Is this Pin latched on startup or does it have to be high all the time? ...

OK, now here is a version with variable arguments

/* *************************************************************************
DESCRIPTION: Implementation of scanf() using CCS ...

And why don't you use the variable arguments list, like the original sscanf?

It's not that I think only this was a problem. I've tried it, and this routine does not work without this little correction. It took a little time ;)

The increment is not the problem, it's this [spam] ...

You have to do a little change, when you want to use this routines with 16bit pointers

long my_atoul(char *s, int16 *endptr, int base)

otherwise *endptr = s; results in an unpridicta ...