• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 21 subscribers
  • Views 775 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
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

Problem with assigning the address of a function to a LIB-variable

norbert christof

I have written a LIB with the following decleration:

  idata u_char clock_occ;
  idata void (*f_ce)(u_char stat);

I use it in the LIB in the way as:

  clock_occ = 1;
  f_ce(TRUE);

so far, no problem, I compile it -> ok:

I add the LIB to my project and use it like:
 
  extern idata u_char clock_occ;
  extern idata void (*f_ce)(u_char stat);

  void SetChipEnable (u_char stat)
  { ... }

  void main (void)
  {
    clock_occ=0;
    f_ce = (void *)SetChipEnable;
  }

-> now I get at the use of "clock_occ" no error, but at the use of "f_ce" I get the warning "1" + "2" (unresolved ex. sym.)

Why?

Many thank's for help.

Norbert Christof

Parents
  • 0 in reply to norbert christof

    I do not see the error, but maybe you want to take a different approach.

    Right now, even if you could get your code to link, you would still need to add an overlay directive. To create the overlay directive properly, you would need to know which library functions used this call back pointer. This defeats the implementation encapsulation that you were probably trying to achieve by using a library.

    My suggestion is to use:

    //in library
extern void f_ce(u_char stat);

//in calling code
void f_ce(u_char stat)
{
  ....
  //use function pointers here if dynamic call backs are needed
}

Reply
  • 0 in reply to norbert christof

    I do not see the error, but maybe you want to take a different approach.

    Right now, even if you could get your code to link, you would still need to add an overlay directive. To create the overlay directive properly, you would need to know which library functions used this call back pointer. This defeats the implementation encapsulation that you were probably trying to achieve by using a library.

    My suggestion is to use:

    //in library
extern void f_ce(u_char stat);

//in calling code
void f_ce(u_char stat)
{
  ....
  //use function pointers here if dynamic call backs are needed
}

Children
  • 0 in reply to Jon Young

    Thanks. I have made this solution:


    In my "lib"

    
defTyp idata void (code*f_ce_on)();  
defTyp idata void (code*f_ce_off)();  


void InitClockLib (u_char *p_ce_on, u_char *p_ce_off)
{
	f_ce_on = p_ce_on;
	f_ce_off = p_ce_off;
}

    .... in a function of the "lib"

      	MCO = 1;
        f_ce_on();

    the using code:

    
void SetChipEnableOn (void)
{
  P2 = 0xFF;
}

void SetChipEnableOff (void)
{
 P2 = 0;				
}

    ... and 

    
InitClockLib ( (u_char*) &SetChipEnableOn, (u_char*) &SetChipEnableOff);

    In the Overlay ... I have to write

    Read ! (SetChipEnableOn, SetUhrChipEnableOff),
Write ! (SetChipEnableOn, SetUhrChipEnableOff)

    Thank for your Help

    Norbert