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

dubug functions

hi everyone i am trying to right a debug funtion SIGNAL as

SIGNAL void function (void)
{
PORT0 = ~ PORT0;
twatch(1000);
}

But when i compile it it gives error

 ****error 6;line 10; syntex error

can anyone figure it out

Parents
  • But the important thing is that defining the line break as a separator is compatible with all existing scripts, while being more forgiving for an end user. And it is easy to do.

    CVS warns about text files ending without a new-line.

    Some text editors has a flag (or hardcoded logic) to automagically add a newline character on the last line of a source file.

    But when designing end-user tools, the design should be as forgiving as possible, without introducing errors or breaking requirements. Since there are no ISO standard requiring these scripts to use the newline as line termination, Keil should correct this unfriendly design choice.

    Even if it takes only 5 seconds for each end user to read the error message and understand it and correct the problem, the accumulated time can be significant.

    This is a small issue. The editor that under specific circumstances doesn't redraw all source lines when scrolling is another. A third is the workspace that sometimes doesn't put the selected source file on top, unless I first click on a different source file. But they seriously affects the feeling of "polished product". That is goodwill that Keil should save for real issues, such as simulation bugs or delayed support of the next super-duper chip.

Reply
  • But the important thing is that defining the line break as a separator is compatible with all existing scripts, while being more forgiving for an end user. And it is easy to do.

    CVS warns about text files ending without a new-line.

    Some text editors has a flag (or hardcoded logic) to automagically add a newline character on the last line of a source file.

    But when designing end-user tools, the design should be as forgiving as possible, without introducing errors or breaking requirements. Since there are no ISO standard requiring these scripts to use the newline as line termination, Keil should correct this unfriendly design choice.

    Even if it takes only 5 seconds for each end user to read the error message and understand it and correct the problem, the accumulated time can be significant.

    This is a small issue. The editor that under specific circumstances doesn't redraw all source lines when scrolling is another. A third is the workspace that sometimes doesn't put the selected source file on top, unless I first click on a different source file. But they seriously affects the feeling of "polished product". That is goodwill that Keil should save for real issues, such as simulation bugs or delayed support of the next super-duper chip.

Children
No data