Serial print, printf , UART "prnts" ...

Value of Serial as debugging tool cannot be overstated, my code is 80% Serial and rest of "real" code. Recently implemented nice TFT_LCD library, guess what - it has its own "Print" class. Works great. Working on video input to my LCD using ATmel code. The demo code came with - what else - another "print" functions. This time based on UART, obvious choice. After years of haggling about it , IDE core code has "standard" printf function. ( NO it is NOT real ANSI standard, but works).

All of these will work "out of box" in applications were they were designed with, non issue.

They step on each other big time when cobbled together!

I am using ARM /Due and seriously considering building class hierarchy to manage these print functions.

Good , bad idea? If good , where should the base class be ? Streams, UART??

I will value any serous opinions / options.

If you do not understand what I am after, ask for more explanations.

I am not asking for any other assistance. There is no specif application , ground is connected, no specific code ( kidding - several thousands of working lines of code ) , no wiring diagram ( OK SPI, USB ) , no video etc available. Sorry.

Happy Halloween ( in US) and good coding to all

Jim

I am using ARM /Due and seriously considering building class hierarchy to manage these print functions.

How many of the libraries that you mention derive from Print? How many implement their own printing capabilities?

What would your print class do that Print() doesn't? How would it be used by classes that don't inherit from Print()?