Thank you, modified my code to include your split //. However, I choose not to use :print:, as that would have problem with Unicode, instead I added ‘use bytes’ to my code.

I still like my own output format better ;-), but I added code to allow user to configure the format (a little bit). 
package StringInspector;

use Hash::Util qw(lock_keys);
use strict;

sub new {
    my $self = {};
    $self->{SUSPECT} = "";
    $self->{BYTES_IN_ROW} = 10;
    $self->{COLUMNS_BETWEEN_PANES} = 5;
    bless $self;
    lock_keys(%{$self});
    return $self;
}

sub inspect {
    my ($self, $string) = @_;
    $self->{SUSPECT} = $string;
}

sub bytes_in_row {
    my $self = shift;
    if (@_) {
        $self->{BYTES_IN_ROW} = shift;
    }
    return $self->{BYTES_IN_ROW};
}

sub columns_between_panes {
    my $self = shift;
    if (@_) {
        $self->{COLUMNS_BETWEEN_PANES} = shift;
    }
    return $self->{COLUMNS_BETWEEN_PANES};
}

sub display {
    use bytes;
    my $self = shift;
    for (my $index = 0; $index <= length $self->{SUSPECT}; $index += $
+self->{BYTES_IN_ROW}) {
        my ($numbers, $chars) = ("", "");
        foreach my $this_char (split(//, substr($self->{SUSPECT}, $ind
+ex, $self->{BYTES_IN_ROW}))) {
            my $ascii = ord($this_char);
            $numbers .= sprintf("0x%0x  ", $ascii);
            $chars .= (($ascii >= 32) and ($ascii <= 126)) ? $this_cha
+r : "."; 
        }
        print $numbers;
        print " " x (6 * $self->{BYTES_IN_ROW} - length $numbers);
        print " " x $self->{COLUMNS_BETWEEN_PANES};
        print $chars;
        print "\n";
    }
}

1;


testing code:
use StringInspector;
use strict;
my $inspector = new StringInspector;
$inspector->bytes_in_row(3);
$inspector->columns_between_panes(40);
$inspector->inspect("abcdefghi" . chr(400) ."jkl");
$inspector->display();

[download]

In reply to Re^3: Is there any garbage chars in your data? (unicode?) by pg
in thread Is there any garbage chars in your data? by pg

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.