[M3devel] HEADS UP: Release engineering, was: Re: CM3 Release

[Randy Coleburn]

There have been a lot of messages flying back and forth on this idea of adding some sort of tagged ref.  I'm afraid I've gotten lost on what exactly is being proposed.
 
Can someone please succinctly state the proposal again along with the reasoning behind why it should be done--what does this change enable us to do that we couldn't do before?  Based on the messages, I'm not sure that Mika, Tony, Rodney, et al are all saying the same thing.
 
Also, not sure I clued into the significance of the LSB value.
 
Regards,
Randy

>>> <hendrik at topoi.pooq.com> 4/17/2009 6:02 PM >>>
On Fri, Apr 17, 2009 at 12:54:13PM +1000, Tony Hosking wrote:
> 
> On 15 Apr 2009, at 02:56, Mika Nystrom wrote:
> 
> >
> >I agree with what Hendrik says, but what about TYPECASE, ISTYPE,
> >NARROW?  Those are necessary to make it possible to pass "pointers"
> >with the low-order bit set outside of unsafe code.
> >
> >My feeling is that if Tony can make the necessary changes, it could
                                                                should
> >be done immediately, and the language issues can be pushed to the
> >future.  But admittedly I'm biased because of the application I'm
> >working on.
> 
> I can take care of this next week.

I'm in favour of trying it out before freezing the feature.  That 
means going ahead now with an implementation, and reconsidering it 
in a few months.  Perhaps marking it experimental with an appropriate 
warning message.  A few months is little enough time to use it that it 
won't be traumatic if code that uses the new features has to be 
partially rewritten.

-- hendrik


CONFIDENTIALITY NOTICE:  This email and any attachments are intended solely for the use of the named recipient(s). This e-mail may contain confidential and/or proprietary information of Scientific Research Corporation.  If you are not a named recipient, you are prohibited from making any use of the information in the email and attachments.  If you believe you have received this email in error, please notify the sender immediately and permanently delete the email, any attachments, and all copies thereof from any drives or storage media and destroy any printouts of the email or attachments.

EXPORT COMPLIANCE NOTICE:  This email and any attachments may contain technical data subject to U.S export restrictions under the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR).  Export or transfer of this technical data and/or related information to any foreign person(s) or entity(ies), either within the U.S. or outside of the U.S., may require export authorization by the appropriate U.S. Government agency prior to export or transfer.  In addition, technical data may not be exported or transferred to certain countries or specified designated nationals identified by U.S. embargo controls without prior export authorization.  By accepting this email and any attachments, all recipients confirm that they understand and will comply with all applicable ITAR, EAR and embargo compliance requirements.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090417/ae2b9dc4/attachment-0002.html>