[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dart
Subject:    Re: [Dart] Ctrl characters in test output
From:       Amitha Perera <perera () cs ! rpi ! edu>
Date:       2002-04-10 18:33:48
Message-ID: 20020410143348.E1522 () cs ! rpi ! edu
[Download RAW message or body]

Hi all

I raised the issue of unprintable character escaping a while ago (see
below). We've run into it again. Although we've changed the test case
to emit only printables, I think Dart should be robust enough to
handle this case.

Is anyone working this?

Thanks,
Amitha.

On Tue, Jan 22, 2002 at 10:16:59AM -0500, Blezek, Daniel J (CRD) wrote:
> Brad, Amitha,
> 
> > > Clearly, such characters need to be escaped somehow. I don't know
> > > enough xml/xsl to know whether the escape should be done client-side
> > > or server side.
> > For some reason we never encountered this problem before, and 
> 
>   This statement isn't quite true, we have seen this a long time ago, and the solution at the time
> was to change the test to _not_ spit out control characters.  I would suggest that we have a look at
> all non-ascii characters and rather than replace them with a "big-red-flag", simply put them in as ^Q
> or whatever.  For some tests, a control character in the output might be what you want, who knows?
> But on the other hand, a "big-red-flag" might also be a good idea.
> 
> -dan
> 
> > proc clean_null_char {str} {
> >      set res ""
> >      set len [string length $str]
> >      for {set i 0} {$i < $len} {incr i} {
> >          set char [string index $str $i]
> >          if {$char != "\0"} {
> >              append res $char
> >          }
> >      }
> >      return $res
> > }
> > 
> > puts [clean_null_char "ab\0cd"]
> > 
> > _______________________________________________
> > Dart mailing list
> > Dart@public.kitware.com
> > http://public.kitware.com/mailman/listinfo/dart
> > 

[prev in list] [next in list] [prev in thread] [next in thread]