Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

Re: Why use strict is good, and barewords are bad

by benizi (Hermit)
on Apr 22, 2005 at 21:24 UTC ( #450585=note: print w/replies, xml ) Need Help??

in reply to Re^3: Why use strict is good, and barewords are bad
in thread Why use strict is good, and barewords are bad

While I like the clever solution to the problem at hand (barewords), I'm much happier that Perl chose the DWIMery of using a default argument of $_, e.g.: perl -Mstrict -lwe 'print for map oct, qw/077 777 034/'

(63, 511, 28) vs. ("oct", "oct", "oct")

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://450585]
[Veltro]: ok, but nm. I meant the solution as a whole actually. Not sincerely the apps that use it
[marto]: and not long ago it wasn't feasible for anyone really to create a finger print of all known music to compare samples against...
[marto]: if you're living in the cloud, you're going to get rained on :P
[Veltro]: feasible in the sense of 'making money'?
[marto]: if your app just calls a remote or third party service to do the task, you app does not 'do the task', it's just a messenger
[marto]: in the sense that for various values of "a while ago" it would not have been possible (and arguable still isn't) to have a fingerprint of every piece of commercially released music to compare against.
[marto]: a co-worker refers to the late 1980s as "a while ago"
[Veltro]: Like I said before, I ment the solution as a whole
[Veltro]: People thought it was not possible.

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (11)
As of 2018-05-24 12:09 GMT
Find Nodes?
    Voting Booth?