The choice of approaches could be made the responsibility of the programmer.
About this quote
- What does it mean?
- The choice of implementation methods could be left to the programmer's discretion.
- In plain terms
- Programmers can decide which approach to use.
- What can you take from it?
- Give developers flexibility in design choices.
Where it applies
Putting it to work
Questions to consider
- When is it better to prescribe an approach?
- What risks arise from too much freedom?
Another view
Too vague to guide concrete action.
More from Larry Wall
You tell it that it's indicative by appending $!. That's why we made $! such a short variable name, after all. :-)
Permalink to quote #115 As someone pointed out, you could have an attribute that says 'optimize the heck out of this routine', and your definition of heck would be a parameter to the …
Permalink to quote #117 Well, that's more-or-less what I was saying, though obviously addition is a little more cosmic than the bitwise operators.
Permalink to quote #114
Related quotes
OOP to me means only messaging, local retention and protection and hiding of state-process, and extreme late-binding of all things. It can be done in Smalltalk…
Alan KayAlan Kay quote #7 There are probably better ways to do that, but it would make the parser more complex. I do, occasionally, struggle feebly against complexity... :-)
Larry WallLarry Wall quote #23 Q. Why is this so clumsy? A. The trick is to use Perl's strengths rather than its weaknesses.
Larry WallLarry Wall quote #295