• State Not Answered
  • Locked Locked
  • Replies 16 replies
  • Subscribers 22 subscribers
  • Views 8603 views
  • Users 0 members are here
Options
Related
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

adding reentrant to typedef function pointers causes redefinition in code

Robert Wilcox

I am porting some code to an 8051.

(header.h)

typedef int     (Writer) (int ,
                                   u_char * ,
                                   u_char ,
                                   size_t ,
                                   u_char * ,
                                   int *) reentrant;
(source.h)
Writer bob;

(source.c)
.
.
.
int     bob(int val1,
            u_char * dat1,
            u_char dat2,
            size_t val2,
            u_char * dat3,
            int *pval) reentrant
{
}

When I attempt to compiler this, I get
error C231: '_bob' : redefinition. If I go to source.h and do the following:
(source.h)
//Comment out Writer bob;
int     (bob)(int val1,
            u_char * dat1,
            u_char dat2,
            size_t val2,
            u_char * dat3,
            int *pval) reentrant;


It compiles fine. Is this a limitation of the compiler? Any shortcuts I could use so I don't have to rewrite large chunks of code

Parents
  • 0 in reply to Robert Wilcox

    "This is code that runs on windows, but was written in a portable manner."

    Trouble is, C51 is an unconventional implementation of 'C' - particularly the way that it does not use the hardware stack for function parameters & locals.
    Conventional 'C' functions are inherently reentrant; C51 functions are inherently non-reentrant.

    Therefore, even the best-designed "portable" 'C' that relies on reentrant functions (as found in 99% of 'C' implementations) will break on C51. :-(

    "I could go back to windows, but the problem is that I will inevitably have to deal with the C51 issues"

    Absolutely - but couldn't that be biting off too much at once?

    I'm just suggesting that you take it a step at a time:
    First, stick with the familiar, conventional Windows environment and remove the reentrancy requirement;
    Then, when you know you've got it working non-reentrant, move it to C51 and address all the other issues (word size, byte ordering, etc, etc)

Reply
  • 0 in reply to Robert Wilcox

    "This is code that runs on windows, but was written in a portable manner."

    Trouble is, C51 is an unconventional implementation of 'C' - particularly the way that it does not use the hardware stack for function parameters & locals.
    Conventional 'C' functions are inherently reentrant; C51 functions are inherently non-reentrant.

    Therefore, even the best-designed "portable" 'C' that relies on reentrant functions (as found in 99% of 'C' implementations) will break on C51. :-(

    "I could go back to windows, but the problem is that I will inevitably have to deal with the C51 issues"

    Absolutely - but couldn't that be biting off too much at once?

    I'm just suggesting that you take it a step at a time:
    First, stick with the familiar, conventional Windows environment and remove the reentrancy requirement;
    Then, when you know you've got it working non-reentrant, move it to C51 and address all the other issues (word size, byte ordering, etc, etc)

Children
No data