JSON decoder

[kmp84]

Hello,

I'm trying to run this JSON decoder ( http://ww1.microchip.com/downloads/en/Appnotes/90003239A.pdf ) with CCS compiler, but have no success yet.

[temtronic]

well 1st 2 errors are in the 'lexer.c' chunk of code, the rest are from 'parser.c'
You'd have to post those for anyone here to decide what is wrong.

it's probably your conversion to CCS C that's causing the errors as different compilers defaults are never the same.....

BTW...the PDF article doesn't have any source code that I could see

[kmp84]

[Ttelmah]

First thing to use MicroChip code, you almost certainly need to set
#DEVICE ANSI
Microchip by default has all it's integers as signed. CCS does not.

Then every reference to 'int' will need to change to 'int16'.

Now the line that fails in parser, in the original file is a blank line. Implies
you must have edited the file, so what we are looking at is not what you
are using.

[kmp84]

Hi,

The "#DEVICE ANSI" directive and int to int16 changed, but has no idea for this:

[temtronic]

It's highly unlikely the code presented by Microchip doesn't work BUT you have to run it on whatever PIC they used and compiler...

I've been caught on the 'device=ans' a couple of times the past, though you've fixed that...
Also check the other 'data definitions or defaults but you should post what errors you're getting.
It could be in your translation into CCS C you've mistyped something, changes a : into a ; or some similar typing error

It's very difficult to 'remotely diagnose what the actual cause of the problem is. For me it's 99.44% a typing error, wished I'd taken 'touch typing' in high school, 1/2 a century+ ago...

[kmp84]

Hi mr. temtronic,

[temtronic]

hmm, there's no 'main.c' in the GitHub link, so no reference as to what PIC was used... Or it might have been an AVR ... Also no mention of which C compiler was used to create the code.
As such, the document is not complete and I'm unable to 'copy/paste/compile/test'.
Others who do this for a living ( I'm retired..) may be able to 'fill in the blanks' and create a workable program ( main.c).

[Ttelmah]

That is because you are including parser.h, after parser.c is being loaded.
The .h files must be included _first_. The compiler does not know what
PARSER_BAD_FORMAT actually 'is'.

Seriously, the code will only be 90% 'compatible'. Everything about
the actual I/O will need to be customised to suit CCS. The ordering of
the files, the declaration of the variables, etc. etc..

[temtronic]

What's curious to me, is that in the original github files, the first line in the parser.c file IS the #include for the parser.h file (same format for the others BTW...)
Puzzling is WHY even have the parser.h file, as it only contains 5-6 lines of code which you need for parser.c, so why not just put them IN the parser.c file ?

Without seeing the complete 'picture' it's hard to diagnose why the failure.

[kmp84]

[Ttelmah]

You are missing the fundamental point.
You can't just take code from one compiler and expect it to compile and
run on another. Though the core 'C' functions are 99% portable, everything
handling I/O, is compiler specific, and has to be adapted by _you_ to
work with a different compiler.
You need to go through the code and work out which lines handle I/O,
and re-code these using the CCS functions. The same applies when moving
from a Raspberry Pi to Microchip, or AVR to PIC.
Code is only 90% portable, not 100%.

[kmp84]

Hi,
Okay mr.Ttelmah,
But in this case there is no specific periphery just ‘standard’ c code and one test string.

[temtronic]

hmm... 'standard' C....
No such thing, several variations of 'C" exist, each compiler has it's own 'set of C'..and DEFAULTS

I believe CCS C is closely based on K&R version of C, though newer versions have added more 'features/functions'...

That's why Mr. T keeps saying you have to read the CCS manual, look for differences in the GitHib posted C code, which actually isn't posted as to WHAT compiler it is.....

[kmp84]

Hi,
I have checked all vars. and types and needs to edit just two int to int16 all others are ok and using ccs’s <stdint.h>.