Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Comparing Object Identity
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Dave Whipp  
View profile  
 More options Dec 12 2002, 5:48 pm
Newsgroups: perl.perl6.language
From: david_wh...@fast-chip.com (Dave Whipp)
Date: Thu, 12 Dec 2002 14:42:49 -0800
Local: Thurs, Dec 12 2002 5:42 pm
Subject: Re: Comparing Object Identity
"Dan Sugalski" <d...@sidhe.org> wrote in message

news:a05200f00ba1ebb73c6d2@[63.120.19.221]...

> There'll definitely be memory address reuse. If .id returns the
> current object's memory address, it shouldn't be cached any place, as
> otherwise you'll find things going bang with some regularity.

In a multi-threaded environment, even a simple

  $a.id == $b.id

may have significant time between the two lookups. If we are
going to rely on addresses for id comparison, then we need to
mandate that the address is constant for the life of the object.
Brent indicated that he could think of no reason for the "header
address" to change: but that isn't strong enough. We need a cast-
iron guarantee. Otherwise we can't compare identity using .id.

Dave.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.