This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

#define statements on variable declarations

Hello. I am trying to find new and exciting ways to optimize (read: shrink down) my current code and want to include an eeprom autorefresh option to cut down on variables. Basically, when I have the AutoRefreshCompile option set, I want it to create the variable "randomvariable". My code is pretty simple:

#define AutoRefreshCompile 1

        #if(AutoRefreshCompile==1)
        {  // line x
                extern signed short randomvariable;
        }  // line y
        #endif

I am getting errors that read as follows:


VARS.H(x) error C141: syntax error near '{'
VARS.H(y) error C141: syntax error near '}'

I'm guessing it is not possible to do this (if I remember correctly, variables have to be declared at the beginning and can't be in the middle of functions/code segments but maybe it's some really simple fix.

I realize this might not work but I figure it's worth a shot. Any suggestions? Thanks!

Parents
  • For the record, if you (or anyone else, really) had told me a few posts ago that my fundamental understanding was in directives vs statements rather than telling me to go find a C book and start reading, it could've saved us all a lot of time. Generic recommendations like "read a book" aren't anywhere near as helpful as saying "you need to read a book about the difference between directives and statements".

    Utter nonsense.
    You would have saved a lot more time if you had actually properly read a C book. As Andrew said, K&R is only 160 pages. Curly brackets and statements is fundamental stuff.
    It's rather obvious that you are not into reading books. Apparently, you prefer to dive into coding and sort out problems through forums. That's OK, but don't expect much sympathy from people who gained knowledge the old-fashioned way. And may I say, your way of learning is rather inefficient.

Reply
  • For the record, if you (or anyone else, really) had told me a few posts ago that my fundamental understanding was in directives vs statements rather than telling me to go find a C book and start reading, it could've saved us all a lot of time. Generic recommendations like "read a book" aren't anywhere near as helpful as saying "you need to read a book about the difference between directives and statements".

    Utter nonsense.
    You would have saved a lot more time if you had actually properly read a C book. As Andrew said, K&R is only 160 pages. Curly brackets and statements is fundamental stuff.
    It's rather obvious that you are not into reading books. Apparently, you prefer to dive into coding and sort out problems through forums. That's OK, but don't expect much sympathy from people who gained knowledge the old-fashioned way. And may I say, your way of learning is rather inefficient.

Children