S06/Lvalue subroutines: "Lvalue subroutines return a proxy object that can be assigned to. (...)"

S13/Methods: "Setter methods that expect the new value as an argument do not fall into the well-behaved category, however."

When I take these two together, in a way which may be out of context for the second but is a fairly obvious interpretation, I get as strong sense of hubris. Setter methods that take arguments are considered bad, but the alternative is horrible ugliness involving explicitly creating and returning proxy arguments??? Anyone who's used Ruby will point to `def foo=' and laugh at you; everyone else will use traditional setters and ignore the whole `is rw' thing as overweening nonsense.

I hope I'm misunderstanding this....

brandon s. allbery [solaris,freebsd,perl,pugs,haskell] [EMAIL PROTECTED]
system administrator [openafs,heimdal,too many hats] [EMAIL PROTECTED]
electrical and computer engineering, carnegie mellon university    KF8NH

Reply via email to