nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TeamSite::DCRnode->new

dinodia

hi all,

i am creating a perl file to read a DCR and parse it to obtain the values. i have used
$rootnode = TeamSite: Smiley Very Happy

CRnode->new($DCRpath);
to do the same, where $DCRPath is the complete path of the DCR.

i am getting an error
XML parse error. not well formed(invalid token)line 1, column 2, byte 2 at c:\teamsite\iw-home\iw-perl\vendor\lib\xml\parser.pm line 187.

i am attaching the dcr..

kindly help me in this regard at the earliest.

thanks,
Deepak Dinodia

Find more posts tagged with

Comments

dinodia

the attachment is here

nipper

Your issue is here:

$rootnode = TeamSite: Smiley Very Happy

CRnode->new($DCRpath);

You are providing a path to a file, this module wants the string of XML/DCR

something like this

open (XML, "$DCRpath") || die "Cannot open $file for reading:$!";
my $xml = join "", ;
close XML;
$rootnode = TeamSite: Smiley Very Happy

CRnode->new($xml );

Adam Stoller

Your issue is here:

$rootnode = TeamSite:CRnode->new($DCRpath);

You are providing a path to a file, this module wants the string of XML/DCR

something like this

open (XML, "$DCRpath") || die "Cannot open $file for reading:$!";
my $xml = join "", <XML>;
close XML;
$rootnode = TeamSite:CRnode->new($xml );

a slightly more efficient slurping method is:

my $xml = do { local $/; <XML> };

/tmp > perl foo.ipl
Benchmark: timing 1000 iterations of ghoti, nipper...
     ghoti:  0 wallclock secs ( 0.04 usr +  0.06 sys =  0.10 CPU) @ 10000.00/s (n=1000)
            (warning: too few iterations for a reliable count)
    nipper:  1 wallclock secs ( 1.01 usr +  0.07 sys =  1.08 CPU) @ 925.93/s (n=1000)
/tmp > perl foo.ipl
Benchmark: timing 10000 iterations of ghoti, nipper...
     ghoti:  1 wallclock secs ( 0.43 usr +  0.70 sys =  1.13 CPU) @ 8849.56/s (n=10000)
    nipper: 11 wallclock secs (10.18 usr +  0.81 sys = 10.99 CPU) @ 909.92/s (n=10000)

The above is from slurping in a 50k file (1416 lines, 4792 characters)

nipper

I knew I was going to get that reply form you.

Adam Stoller

I knew I was going to get that reply form you.

I didn't want to let you down ;-)

kaalraa

In earlier days i heard from someone - It's always better to use 'Preview Post'. Hope it applies for everyone and one should take care for the same. Smiley Happy

Nothing offensive.

gzevin

I knew I was going to get that reply form you.

not that, but something was meant to come... He's mean and evil that fishy guy Smiley Happy

dinodia

it worked.. thanks