On 2008 May 15, at 1:30, Me Here wrote:
"John M. Dlugosz" wrote:
no strong_type_check :rw
in scope can turn that off, in case you want to play dirty tricks.
What is the point of be able to mark things readonly if the compiler
does reject assignment attempts?
(assuming you meant "doesn't")
What is the point of marking things readonly if you can turn it off?
Documentation.
Backward type-API compatibility.
I am unsure at this point if this applies to Perl 6, but in Haskell it
is possible to do in-place update by diving into IO behind the scenes
with (read-only by default) data structures. In this case "is ro"
would be a reminder that the caller has expectations that you must be
careful not to violate while you're working behind the curtain.
--
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
