Re: memory safety and weak references

2013-03-28 Thread Oliver Hunt
On Mar 29, 2013, at 7:36 AM, David Herman wrote: > On Mar 27, 2013, at 4:52 AM, Sam Tobin-Hochstadt wrote: > >> On Tue, Mar 26, 2013 at 11:44 PM, Oliver Hunt wrote: >>> That said I believe that this does kill any dreams i may have had w.r.t >>> primitive-keyed WeakMaps, kudos to MarkM. >> >

Re: endianness (was: Observability of NaN distinctions — is this a concern?)

2013-03-28 Thread David Herman
On Mar 27, 2013, at 6:51 AM, Andreas Rossberg wrote: > There actually are (third-party) projects > with ports of V8 and/or Chromium to big endian architectures. It would be helpful to have more information about what these platforms and projects are. > WebGL > code should not break or become p

Re: endianness (was: Observability of NaN distinctions — is this a concern?)

2013-03-28 Thread Mark S. Miller
"prohibitively" depends on your tolerance. Modern machines can usually do register-to-register byte order reversal rather speedily. Which big endian machines do you have in mind? On Wed, Mar 27, 2013 at 6:51 AM, Andreas Rossberg wrote: > On 27 March 2013 00:35, David Herman wrote: > > [breaking

Re: memory safety and weak references

2013-03-28 Thread David Herman
On Mar 27, 2013, at 4:52 AM, Sam Tobin-Hochstadt wrote: > On Tue, Mar 26, 2013 at 11:44 PM, Oliver Hunt wrote: >> That said I believe that this does kill any dreams i may have had w.r.t >> primitive-keyed WeakMaps, kudos to MarkM. > > Wouldn't a primitive-keyed WeakMap just be a strong Map for

Re: memory safety and weak references

2013-03-28 Thread David Bruant
[answering to different messages at once] [cc'ing Oliver Hunt as Apple representative and Luke Hoban as Microsoft representative for questions at the bottom] Le 27/03/2013 23:47, Brendan Eich a écrit : You have it backwards. You are advocating a GC design monoculture (exact rooting only) My po