hi
i am a newbie here. i urgently need any new functions that can be used in c. it must be good and have algorithm description. no bugs allowed. your help will be much appreciated.
thanks
www.catb.org/.../smart-questions.html
Why is it so "urgent"?
"i am a newbie here"
Do you have any prior programming experience?
Do you have any prior microcontroller experience?
"i urgently need any new functions that can be used in c"
Have you really exhausted all the old functions that already exist in 'C'?
eg, http://www.keil.com/download/list/c51.htm
Note that functions are usually specified in terms of the inputs they take, the actions they perform, and the outputs that they return - their age ("new" or "old") is not usually relevant...
Of course the age is important. They slowly wear out and tire, so a young student of course needs young fresh blood.
Besides, it's the aspect of how much published the functions are. Better with a brand new function, so the school anti-cheat software doesn't find too many matches when comparing the text of the school turn-in report with existing documents/code on the net.
i urgently need any new functions that can be used in c. it must be good and have algorithm description. no bugs allowed
I want it for free and you better have spent a long time testing and documenting it before you give it to me.
If you need some specific functions, I'll gladly provide them at my usual rate
Erik
// Function Name: one() // Accepts: None // returns: 1 // comments: None int one(void) { return 1; // return 1 }
are you sure you did enough testing and where is the algorithm description
remember must be good and have algorithm description. no bugs allowed
It definitely needs a flowchart.
I was going to get a full function header template. But the work involved exceeded the point and amusement values.
I could do the flow chart......
here is my entry:
//function: do nothing but bug_free function in c void do_nothing(void) { }
http://www.keil.com/support/man/docs/c51/c51_c275.htm
I said bug free, not warning free.
notice the distinction?
An empty function can now and then be very good to use, since they normally do have interesting side effects.
For compilers that doesn't to global optimization, they can be used as execution barriers, having the compiler store or reload global variables.
#pragma TREAT_WARNINGS_AS_BUGS(1)
I typically start my project top down. so in the early stages of a project, it is often the case that 90%+ of my code are empty functions.
"since they normally do have interesting side effects."
like what?