Re^4: Easy XML-parser that can handle large file?

a 'nice' from the module author... i'm honored... ;=)

I never noticed this feature of $_ set to $_[1] (or well, i used incosciously..)

May be worth to add some line in the Synopsis:

para    => sub { $_[1]->set_tag( 'p')  }, # change para to p (handlers
+ receive $twig and $element as argouments)
para    => sub { $_->set_tag( 'p')  },    # change para to p ($_ is al
+iased to $_[1] for convenience  )


###and in the corpus of the docs:

$_ is also set to the element (ie: $_[1]), so it is easy to write inli
+ne handlers like
[download]

There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.

Comment on Re^4: Easy XML-parser that can handle large file? Select or Download Code

Replies are listed 'Best First'.
Re^5: Easy XML-parser that can handle large file? by mirod (Canon) on Sep 12, 2014 at 08:30 UTC
The first example in the synopsis uses `$_`, I added a comment to make it more explicit. It's also mentioned in the XML::Twig 101 section. I know that the docs are a bit overwhelming and hard to read. The main reason is probably that XML::Twig it's too big. This comes from a decision I made, a long time ago, to have just 1 massive module, instead of several ones. The reason at the time was to allow users to install the module easily, especially on Windows, by simply copying Twig.pm in the proper place. At the time there were no Strawberry Perl, perlbrew or local::lib... If I were to start again I would certainly break up the module in several sub-modules (as with XML::Twig::XPath).	[reply] [d/l]

Replies are listed 'Best First'.

Re^5: Easy XML-parser that can handle large file?
by mirod (Canon) on Sep 12, 2014 at 08:30 UTC

The first example in the synopsis uses $_, I added a comment to make it more explicit. It's also mentioned in the XML::Twig 101 section.

I know that the docs are a bit overwhelming and hard to read.

The main reason is probably that XML::Twig it's too big. This comes from a decision I made, a long time ago, to have just 1 massive module, instead of several ones. The reason at the time was to allow users to install the module easily, especially on Windows, by simply copying Twig.pm in the proper place. At the time there were no Strawberry Perl, perlbrew or local::lib... If I were to start again I would certainly break up the module in several sub-modules (as with XML::Twig::XPath).

[reply]
[d/l]