Front page | perl.perl5.porters |
Postings from May 2000
On Mon, May 22, 2000 at 11:04:12PM -0700, "Yitzchak Scott-Thoennes" wrote:
> In article <20000523001623.A7317@pcard12x.ca.nortel.com>,
> "Mark Mielke" <markm@nortelnetworks.com> wrote:
> > On Mon, May 22, 2000 at 03:34:54PM -0600, "Tom Christiansen" wrote:
> > > It's like passing a law against naughty thoughts. Or against
> > > suicide. Neither has any beneficial effect whatsoever, because the
> > > determined will always be there to circumvent your wishes. Only
> > > education helps.
> > You are mistaken.
> > The law is already passed; what is being considered is enforcement at
> > a level that be effective even against the incompetent.
> I think I agree with Tom. I didn't feel I completely understood the
> point of Mark Summerfield's message to which Tom was replying, but the
> gist of it seemed to me to be that there should be some way of
> ...
I didn't disagree with Tom specifically. More I disagreed with one of
his many mistaken analogies that are used to prove "points." Discussion
should stay with logic and not get side tracked by things like this.
> If someone wants a constant $pi of 3.1415926535897932 and then later
> says *pi=\'gimme a slice', then that is what they want done.
> Apologies if I misunderstood Mark S's point.
All that being said, it is currently impossible to create a true constant
in the SV slot of a glob (or in a lexical for that manner) without use of
XS/C code.
If this feature was added, why shouldn't a glob be able to be
explicitly declared readonly as well? (after having set the slots up as
desired)
Everyone would then be satisfied.
mark
--
markm@nortelnetworks.com/mark@mielke.cc/markm@ncf.ca __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | SIR Tools (7H12)
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ | Nortel Networks
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
Thread Previous
|
Thread Next