<br><br><div class="gmail_quote">On Tue, May 29, 2012 at 12:32 AM, James Aylett <span dir="ltr"><<a href="mailto:james-xapian@tartarus.org" target="_blank">james-xapian@tartarus.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF"><div>I'd favour either complaining about overflow of numbers rather than types, or auto-convert to strings so it's a bit more like using twitter snowflake ids. Or I guess something like the math.Long trick from Closure.</div>
</div></blockquote><div><br>Isn't it poor form to work for a time and then overflow without warning? As for a workaround, I'd want to know how users need to manipulate doc ids in JS before choosing a hack...<br></div>
<div bgcolor="#FFFFFF"><div><br></div></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><div>Any idea when v8 will get 64 bit support? Or is this not on the roadmap at all?</div>
</div></blockquote><div><br>They're under discussion for the next draft of the ECMA standard, I believe. <br></div><div bgcolor="#FFFFFF"><div><br></div></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"><div>On arrays, is there no way of deferring comprehension until later? So you could pass an array-like object around and slice it later.<br></div></div></blockquote><div><br>Comprehension? Slice? Sorry I've not run across those terms in this context.<br>
<br>Once can define "getter" function members in an object or prototype (class); accessing the member implicitly invokes the function. However we wouldn't use that mechanism to perform I/O, as getters only function synchronously.<br>
<br></div></div>