Re: Mojo::DOM exception handling help

This is only an educated guess here, as I don't have the facilities currently to test, nor the time to read docs to understand what's happening. Can you extract the object, check for defined, then act appropriately?

Instead of:

my $abstr = $dom1->at('div.abstract-content > p' || 'not provided')->t
+ext;
[download]

Will something like this example work?:

my $obj   = $dom1->at('div.abstract-content > p' || 'not provided');
my $abstr = defined $obj ? $obj->text : 'Object undefined';
[download]

If it does work, you could elaborate on it a little, to say log the entries that are broken.

Comment on Re: Mojo::DOM exception handling help Select or Download Code

Replies are listed 'Best First'.
Re^2: Mojo::DOM exception handling help by haukex (Archbishop) on Aug 01, 2020 at 19:15 UTC
To the OP: Without having the time to test myself at the moment, what stevieb suggested should work; you can also choose a different action to take with a more complex statement like `if ( defined $obj ) { ... } else { ... }`. Note that `'div.abstract-content > p' \|\| 'not provided'` is actually not doing anything useful, as it's just a logical or and the first value is always true, so the second value will always be ignored.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: Mojo::DOM exception handling help
by haukex (Archbishop) on Aug 01, 2020 at 19:15 UTC

To the OP: Without having the time to test myself at the moment, what stevieb suggested should work; you can also choose a different action to take with a more complex statement like if ( defined $obj ) { ... } else { ... }. Note that 'div.abstract-content > p' || 'not provided' is actually not doing anything useful, as it's just a logical or and the first value is always true, so the second value will always be ignored.

[reply]
[d/l]
[select]