On Thu, 21 Sep 2000, Tom Christiansen wrote: > =item perl6storm #0050 > > Radical notion: consider removing precedence. > Wrong precedence makes people miserable. (Some people already suggest that Perl only has two precedence rules: (1) multiplication and division come before addition and subtraction, and (2) parenthesize everything else.) This would make Perl more like Lisp, I suppose. But it would make code less ambiguous, probaly at the cost of readability. Arguably, some (most?) of the precedence levels already work the way people expect them to (for example, == binds more tightly than || or &&), so fewer "cluttering" parentheses are needed to make things readable while still being correct. Cheers, Philip -- Philip Newton <[EMAIL PROTECTED]>
- Re: PERL6STORM - tchrist's brainstorm list for perl6 Tom Christiansen
- "0", true or false? (was: PERL6STORM #0052) Bart Lateur
- Re: "0", true or false? (was: PERL6STORM #... David L. Nicol
- Re: "0", true or false? (was: PERL6STO... Nathan Wiger
- auto-flock on file open (was: PERL6STORM - #0031) Bart Lateur
- perl6storm #0010: kill all defaults Philip Newton
- perl6storm #0011: interactive perl mode Philip Newton
- Re: perl6storm #0011: interactive perl mode Russ Allbery
- Re: PERL6STORM - tchrist's brainstorm list for perl6 Philip Newton
- Re: perl6storm #0050 Philip Newton
- Re: perl6storm #0050 raptor
- Re: perl6storm #0050 Dave Storrs
- Re: perl6storm #0050 Johan Vromans
- Re: perl6storm #0050 John Porter
- Re: perl6storm #0050 Simon Cozens
- Re: perl6storm #0050 Robert Mathews
- Re: perl6storm #0050 Simon Cozens
- Re: perl6storm #0050 Piers Cawley
- Re: perl6storm #0050 Simon Cozens
- Re: perl6storm #0050 Piers Cawley