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

not able to use printf statement in keil uvision 4

not able to use printf statement in keil uvision 4

Parents
  • Of course. You decided to try to lie to the compiler and making a false claim.

    A $20 bill will still be a $20 bill even if you try to tell someone it is a $100 bill.

    That function takes the arguments that it did when Keil compiled the C runtime library. And Keil implemented their runtime library based on the C language standard. Trying to lie to the compiler and claim strstr() takes different data types by writing a new function prototype is not the route to go.

    So did you try out Google? Didn't you see any answers that seemed relevant to your problem? What is your view on type casts? What they are? And if they may be applicable to this problem? Would a type cast be able to keep the compiler happy, while also make strstr() still perform a correct job?

Reply
  • Of course. You decided to try to lie to the compiler and making a false claim.

    A $20 bill will still be a $20 bill even if you try to tell someone it is a $100 bill.

    That function takes the arguments that it did when Keil compiled the C runtime library. And Keil implemented their runtime library based on the C language standard. Trying to lie to the compiler and claim strstr() takes different data types by writing a new function prototype is not the route to go.

    So did you try out Google? Didn't you see any answers that seemed relevant to your problem? What is your view on type casts? What they are? And if they may be applicable to this problem? Would a type cast be able to keep the compiler happy, while also make strstr() still perform a correct job?

Children