This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Re: diag_printf refuses to print ANSI escape sequences?


On Mon, May 28, 2007 at 10:29:02AM -0700, Paul D. DeRocco wrote:
> > From: Sergei Gavrikov
> > 
> > Why is here this flame? If you need to expand the 
> > diag_printf() add own CDL rule to expand that diag_check_string ():
> > 
> > if( c == '\n' || c == '\r' || c == '\b' || c == '\t' || c == '\E' )
> >     continue;
> > 
> > Gary already did point on that.
> 
> Or perhaps a CDL rule to turn off the string checking entirely. I'll bet

It seems, that isn't good idea to turn off string checking at all in the
diagnostic function. LF, CR, BS and TAB are the essentials of the text
formating. So, those chars are there. The '\b' quite could produce a
bold printing, in past, for example :-) Sometimes, it needs to expand
TAB to spaces and etc. Other non-printed characters are optional things.
This is just _my_ opinion.  I think that minimalist set ('\n', '\r',
'\b', '\t') was the enough set for the diag_print() application.

-- Sergei

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]