it's certainly not intractable, at least. But to a fellow embedded developer, I would be surprised if anyone were confused by the use of standard library string functions? One can even write with wholly original functions and have it be.
CODEVISION RETURN PC
Comparing, say, PC to embedded development, the greater diversity of functions needed/used, and the lack of IO abstraction, makes things different, sure. Good communication comes when familiar structures are understood by both parties, and this can occur with any set of functions. There's no guarantee that one will write clear code, nor any that someone else will find it easy to understand. Don't forget, printf itself can be abused. One can always write a mess, and a mess is always going to be a mess. Specifically: (ah nice, the forum search found it easily for once!) Yeah, I wouldn't be so harsh about it. (and all the other friends in ) on embedded systems. Often better to use simple string functions, like itoa(), puts(), etc.
CODEVISION RETURN CODE
It's a very heavy-weight function, adding a lot of code that you're probably never going to use. BTW, it may be worth avoiding use of printf() and friends.
CODEVISION RETURN SOFTWARE
Software yang digunakan untuk membuatkan list program ini adalah Software CodeVision AVR. It is then trivial to pipe the output into a logfile say (if you happen to add logging at some point), or test the code on PC (it's portable), etc. Apabila sobat telah selesai membuat gambar rangkaian diatas dengan menggunakan software proteus dengan baik dan benar, maka langkah selanjutnya adalah membuatkan list program untuk input keypad dan output LED. I suppose the most "proper" way, is to implement an interface for each port, and open them in respective files. Mind, this may corrupt output due to buffering - make sure to flush buffers before changing things over (or choose an unbuffered file mode or whatever). You could cheat it at this point, by changing what your callback outputs to.
You have to implement that yourself (usually with callback functions). In any case, on an MCU, you of course don't have an operating system providing the underlying functionality. You can open a file and use fprintf() to write to stdout, stderr, CON, COM1, /dev/ttyS0, etc., whatever you like. printf() uses the default CON so you're kind of stuck with that (and however it's assigned by libc (I forget exactly), or whatever CodeVision is using).
You want to print to CONsole two different ways what sense does that make? Well, operating systems do often have multiple ways, but you have to specify what.
0 kommentar(er)
