From: "Paul D. DeRocco" <pderocco@ix.netcom.com>
To: "'Sergei Gavrikov'" <w3sg@SoftHome.net>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Re: diag_printf refuses to print ANSI escape sequences?
Date: Mon, 28 May 2007 20:22:00 -0000 [thread overview]
Message-ID: <004e01c7a14d$af6fec50$887ba8c0@PAULD> (raw)
In-Reply-To: <1180345081.16789.23.camel@sg-ubuntu>
> 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
most people had no idea it was in there at all, until this thread came up.
It's certainly unexpected behavior to me. I would have expected diagnostic
output to be lightweight, with minimum built-in cleverness. So would the OP,
apparently.
--
Ciao, Paul D. DeRocco
Paul mailto:pderocco@ix.netcom.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-05-28 17:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 16:38 [ECOS] " Grant Edwards
2007-05-26 20:19 ` Sergei Gavrikov
2007-05-26 22:56 ` [ECOS] " Grant Edwards
2007-05-27 10:12 ` Gary Thomas
2007-05-27 14:42 ` Sergei Gavrikov
2007-05-28 5:33 ` Grant Edwards
2007-05-28 15:28 ` Sergei Gavrikov
2007-05-28 20:22 ` Paul D. DeRocco [this message]
2007-05-28 20:33 ` Sergei Gavrikov
2007-05-29 4:50 ` Paul D. DeRocco
2007-05-29 9:57 ` Nick Garnett
2007-05-29 17:05 ` Grant Edwards
2007-05-29 7:45 David Fernandez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='004e01c7a14d$af6fec50$887ba8c0@PAULD' \
--to=pderocco@ix.netcom.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=w3sg@SoftHome.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).