• State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 21 subscribers
  • Views 1531 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

L13 Warnings don't make sense

Chris Beattie

I decided to start a new thread since this problem is different than the original one.

When I compile the attached code, I get four L13: Recursive Call to Segment Warnings. One of the functions called out in the warnings is this one:

BYTE process_Help(char xdata *cmdBuf)
{
    printf("\r\nP2_CMDHELP\r\n");
    printf(cmdBuf);
    cmdBuf[0] = '\0';
    printf( "\r\nHelp Message\r\n"
    return TRUE;
}

which is obviously not recursive. If anyone can figure this out, it would be greatly appreciated. You can download the code from:

http://briefcase.yahoo.com/bc/cbeattie/lst?.dir=/Keil&.view=l

You'll need to correct Keil's standard reg530.h file with standard C/C++ include file protection by adding this to reg530.h:

// First two lines of corrected reg530.h
#ifndef _REG530_H
#define _REG530_H
.
.
.
#endif  // Last line of corrected reg530.h

In order for the code to compile.

Thanks,
Chris Beattie

Parents
  • 0 in reply to Chris Beattie

    looks like one thing Keil can work on

    the warning message or the use of function pointers?

    I certainly think there's loads of room for improvement in the Errors helpfile; it's a brilliant idea with the description, then Symptoms, Cause, and Example - but often poorly implemented or just left blank.

    A missed opportunity so far, I think.

    It's certainly high time they got the F1 message help to work properly!

Reply
  • 0 in reply to Chris Beattie

    looks like one thing Keil can work on

    the warning message or the use of function pointers?

    I certainly think there's loads of room for improvement in the Errors helpfile; it's a brilliant idea with the description, then Symptoms, Cause, and Example - but often poorly implemented or just left blank.

    A missed opportunity so far, I think.

    It's certainly high time they got the F1 message help to work properly!

Children
No data