Typedef conversion for ANSI compliance

crystal_lattice · Joined: 13 Jun 2006 Posts: 164

Hi there. I'm having problems with typedef conversions. I'm busy trying to implement the fat lib at http://elm-chan.org/fsw/ff/00index_e.html. It's apparently ANSI C compatible and has a include file to handle type conversions for non ANSI compilers AKA CCS.

My v4.057 compiler does not like this file, on the first line it warns "Expecting an identifier" which I can understand as an INT already has a "meaning" to the compiler but how can I overcome this problem other than re-writing all the code. I looked in the help file on the topic of typedef but doesn't help much. I have however found the "#Type" directive but am not sure if this will do what I want it to. I have included my modified version of the code but it gives me a compiler warning "Expresion must evaluate to a constant" Am I on the right track or using functions for the wrong purpose? Secondly, is the "enum" function used correctly, as I don't see the need for the "bool" at the end, and is the function actually needed?

Thanx in advance

PS. Anybody had any luck with this FAT lib??

here is the original file:

Fusillade · Joined: 02 Aug 2007 Posts: 31

Have you tried removing the data type from the expressions? It is unnecessary for what you are trying to do.

You want TYPE to change the length of the default type. Since INT is normally 8 bits, by using #TYPE INT=16, you have made INT equal to 16 bits. You can also use #TYPE SIGNED to make all default uses of the word as signed. As a result, INT should now be 16 bit signed. Then you use typedef to change unsigned INT to UINT which should now be 16 bit unsigned.

Try:

crystal_lattice · Joined: 13 Jun 2006 Posts: 164

Hi again. I tried the changes as suggested but the compiler gets stuck on the "#TYPE CHAR=8" line with message "Expresion must evaluate to a constant" and when i comment this line out, it gets stuck on the "typedef enum { FALSE=0, TRUE };" line meth message "Expecting and identifier". Any other suggestions???

Kind Regards

Guest · Posted: Wed Jan 30, 2008 12:27 am

dyeatman · Joined: 06 Sep 2003 Posts: 1968 Location: Norman, OK

You are trying to redefine the Char and Bool types that are already standard defaults (Pg 37 in the current manual).

Read the #Type definition section of the manual. It tells you the allowed standard types for the #Type pre-processor (pg 115 in the current manual)

ak6dn · Joined: 08 Jan 2006 Posts: 23 Location: Saratoga, CA USA

crystal_lattice · Joined: 13 Jun 2006 Posts: 164

Update: Inserting the #case at the top of the file causes other problems; compiler stops at "typedef unsigned INT UINT;" line with warning "Expecting a ; or,". Removing the #case causes my previous problems to come back!! I fixed the "typedef enum { FALSE=0, TRUE }Bool;" but still warning "Expecting identifier" Any other hints??

PS. If I'm not mistaken the compiler is case insensitive and using #case makes it case sensitive

Kind Regards

Ken Johnson · Joined: 23 Mar 2006 Posts: 197 Location: Lewisburg, WV

Break it apart - fix one piece at a time - then put the working parts back together. I think you can get there Smile

Ken

ak6dn · Joined: 08 Jan 2006 Posts: 23 Location: Saratoga, CA USA

Fusillade · Joined: 02 Aug 2007 Posts: 31

crystal_lattice · Joined: 13 Jun 2006 Posts: 164

Hi guys, I kinda got the code working with the mods you guys did - thanks a lot! I'am running in to other problems now further down the line. Some of the function declarations are causing problems "FRESULT f_open (FIL*, const char*, BYTE);" is giving warning "Expecting identifier" I suspect it has something to do with a pointer pointing to a constant?? Here is the header of the function:

Ken Johnson · Joined: 23 Mar 2006 Posts: 197 Location: Lewisburg, WV

I've had problems with "const char *" in a function def or prototype. The compiler should accept this - it just says your code can't modify char(s). Oh, well . . .

Ken