Re: xml question for xml::twig

2008-11-15 Thread Richard Lee
Richard Lee wrote: Chas. Owens wrote: my $sabal = new XML::Twig( twig_roots => { 'foo/yahoo' => #'[EMAIL PROTECTED]"kingtony"]' => sub { my ($yabal, $element ) = @_;

Re: xml question for xml::twig

2008-11-15 Thread Richard Lee
Chas. Owens wrote: Perhaps I am dense, but what is the desired output from the given XML? Hello Chas, From xml file, based on attribute value for bayking id, I want to find kingtony and then I want to traverse back up to yahoo and print everything from to I have tried to use xpath

Re: xml question for xml::twig

2008-11-15 Thread Chas. Owens
On Sat, Nov 15, 2008 at 23:18, Richard Lee <[EMAIL PROTECTED]> wrote: > Richard Lee wrote: >> >> Chas. Owens wrote: >>> >>> On Sat, Nov 15, 2008 at 16:27, Richard Lee <[EMAIL PROTECTED]> wrote: >>> snip >>> if ( $bay1->att('id' eq 'kingtony' ) ) { >>> >>> snip >>> >>> I thi

Re: xml question for xml::twig

2008-11-15 Thread Richard Lee
Richard Lee wrote: Chas. Owens wrote: On Sat, Nov 15, 2008 at 16:27, Richard Lee <[EMAIL PROTECTED]> wrote: snip if ( $bay1->att('id' eq 'kingtony' ) ) { snip I think you mean to say if ($bay1->att("id") eq "kingtony") { yes, that was a typo... I changed to my $sabal

Re: xml question for xml::twig

2008-11-15 Thread Richard Lee
Chas. Owens wrote: On Sat, Nov 15, 2008 at 16:27, Richard Lee <[EMAIL PROTECTED]> wrote: snip if ( $bay1->att('id' eq 'kingtony' ) ) { snip I think you mean to say if ($bay1->att("id") eq "kingtony") { yes, that was a typo... -- To unsubscribe, e-mail: [EMAIL PROTECTE

Re: xml question for xml::twig

2008-11-15 Thread Chas. Owens
On Sat, Nov 15, 2008 at 16:27, Richard Lee <[EMAIL PROTECTED]> wrote: snip >if ( $bay1->att('id' eq 'kingtony' ) ) { snip I think you mean to say if ($bay1->att("id") eq "kingtony") { -- Chas. Owens wonkden.net The most important skill a programmer can have is the ability to read.

Re: xml question for xml::twig

2008-11-15 Thread Richard Lee
use strict; use warnings; use XML::Twig; my $xml = < 1 yes 10 no emmigrate="no">

Re: [PBML] Quoting hash keys changes things sometimes

2008-11-15 Thread Chas. Owens
On Sat, Nov 15, 2008 at 17:42, Jenda Krynicky <[EMAIL PROTECTED]> wrote: snip > The rule for automatic quoting within $hash{...} is "if it looks like > word, it doesn't have to be quoted". And - is not in the list of word > characters as far as Perl is concerned. snip Not exactly. A hyphen is all

Re: Quoting hash keys changes things sometimes

2008-11-15 Thread Rob Dixon
Kelly Jones wrote: > Consider: > > perl -le '$hash{"foo-bar"} = 1; print $hash{foo-bar}' > [no result] > > perl -le '$hash{"foobar"} = 1; print $hash{foobar}' > 1 > > I sort of understand this: in the first script, Perl treats foo-bar as > a subtraction, and sets $hash{0} to 1. In the second one

Re: [PBML] Quoting hash keys changes things sometimes

2008-11-15 Thread Jenda Krynicky
From: "Kelly Jones" <[EMAIL PROTECTED]> > Consider: > > perl -le '$hash{"foo-bar"} = 1; print $hash{foo-bar}' > [no result] > > perl -le '$hash{"foobar"} = 1; print $hash{foobar}' > 1 > > I sort of understand this: in the first script, Perl treats foo-bar as > a subtraction, and sets $hash{0} to

xml question for xml::twig

2008-11-15 Thread Richard Lee
Hello, I am praticing below XML file. Based on where I find att id for bayking id 'kingtony' , I wanted to print out the entire element/att(and ID) and any text found from to .(exception of bayqueen_list and its descendatns)... I am having problem just print out one value... can someone take

Re: Quoting hash keys changes things sometimes

2008-11-15 Thread Chas. Owens
On Sat, Nov 15, 2008 at 15:10, John W. Krahn <[EMAIL PROTECTED]> wrote: snip > s/pargmas/pragmas/; snip And I had paragams at one point. I need more (or better) sleep. -- Chas. Owens wonkden.net The most important skill a programmer can have is the ability to read. -- To unsubscribe, e-mail:

Re: Quoting hash keys changes things sometimes

2008-11-15 Thread John W. Krahn
Chas. Owens wrote: On Sat, Nov 15, 2008 at 13:52, Kelly Jones <[EMAIL PROTECTED]> wrote: Consider: perl -le '$hash{"foo-bar"} = 1; print $hash{foo-bar}' [no result] perl -le '$hash{"foobar"} = 1; print $hash{foobar}' 1 I sort of understand this: in the first script, Perl treats foo-bar as a s

Re: Quoting hash keys changes things sometimes

2008-11-15 Thread John W. Krahn
Kelly Jones wrote: Consider: perl -le '$hash{"foo-bar"} = 1; print $hash{foo-bar}' [no result] Using warnings and/or strict may have helped: $ perl -Mwarnings -le 'my %hash = ("foo-bar", 1); print $hash{foo-bar}' Unquoted string "foo" may clash with future reserved word at -e line 1. Argument

Re: Quoting hash keys changes things sometimes

2008-11-15 Thread Chas. Owens
On Sat, Nov 15, 2008 at 13:52, Kelly Jones <[EMAIL PROTECTED]> wrote: > Consider: > > perl -le '$hash{"foo-bar"} = 1; print $hash{foo-bar}' > [no result] > > perl -le '$hash{"foobar"} = 1; print $hash{foobar}' > 1 > > I sort of understand this: in the first script, Perl treats foo-bar as > a subtra

Quoting hash keys changes things sometimes

2008-11-15 Thread Kelly Jones
Consider: perl -le '$hash{"foo-bar"} = 1; print $hash{foo-bar}' [no result] perl -le '$hash{"foobar"} = 1; print $hash{foobar}' 1 I sort of understand this: in the first script, Perl treats foo-bar as a subtraction, and sets $hash{0} to 1. In the second one it assumes you just left off some quot