&& $__->{product} && $__->offers && $__->{
$product_id } && $__->{name}
2, &&$ operator, which can be used like that:
my $pname = $self->{db &&$ ->{product} &&$ ->offers &&$ -> {
$product_id } &&$ ->
st would work how you want it to...
\---
Where I can find the "reduce" command? I understand how it works,
but this is *VERY* dirty.
The $pname=eval{ ... } block is much cleaner...
But what about the suggestion? Is it a good suggestion?
How will I make it formal?
dLux
--
perl -e 'print
$i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
;eval $scalar"!
This syntax should remain for small dirty scripts.
Most of the work should be done with "no strict" mode.
My suggestion is: declare "eval $scalar" as a bad guy.
Comments? (I may write an RFC if it worth...)
dLux
--
..all in all it's just another rule in the firewall. /Ping Flood/
/--- On Fri, Aug 04, 2000 at 05:58:44PM +0100, Piers Cawley wrote:
| > At 02:31 PM 8/4/00 +0200, dLux wrote:
| > > My suggestion is: declare "eval $scalar" as a bad guy.
| > It's not just string eval. It's also do FILE and require.
| > It's a pow
t is
clear, I want to take part in the detailed design of the
implementation.
dLux
--
"Don't THINK you are - KNOW you are"
(Morpheus, The Matrix)
with those things.
dLux
--
([EMAIL PROTECTED], http://www.dlux.hu)
/--- On Mon, Sep 04, 2000 at 07:18:56PM -0500, Greg Rollins wrote:
| Will perl monitor the commit and rollback actions of transactions?
\---
What exactly you mean?
dLux
--
This message is READ-ONLY
