On Fri, Jun 21, 2013 at 3:55 AM, wrote:
> On Thursday, June 20, 2013 9:53:01 AM UTC-7, Bill McCloskey wrote:
>> It looks like ProxyClass is only used for the "Proxy" object that we add to
>> the global (i.e., the thing that allows you to do Proxy.create). That object
>> isn't actually a proxy a
On 6/14/13 6:11 PM, Bill McCloskey wrote:
Finally, are we allowed to use filenames that overlap with filenames
elsewhere in gecko?
How well do debugger "break filename:lineno" commands handle that?
-Boris
___
dev-tech-js-engine-internals mailing list
On Thursday, June 20, 2013 9:53:01 AM UTC-7, Bill McCloskey wrote:
> It looks like ProxyClass is only used for the "Proxy" object that we add to
> the global (i.e., the thing that allows you to do Proxy.create). That object
> isn't actually a proxy at all. It probably would make sense to rename
On 06/14/2013 02:55 PM, Nicholas Nethercote wrote:
> I propose that we do the following: take the full path within js/src,
> replace '/' and '.' with '_', and add two underscores to the end. For
> example:
>
> - jsapi.h: jsapi_h__
> - gc/Barrier.h: gc_Barrier_h__
> - vm/Stack.h: vm_Stack_h__
Brian and I had the unfortunate experience this Monday that the rules regarding
the required or allowed actions with regard to revisions that cause performance
regressions aren’t well enough defined. Or at least that there is some room for
improvement. So the intention of this post is for everyo
On 6/14/13 8:32 PM, Nicholas Nethercote wrote:
ps: just for laughs, I looked at what Gecko does. Consistency does
*not* abound, and double and triple underscores are frequent.
New additions to Gecko have been using basically what you'd put in the
#include string, with '/' and '.' replaced by
On 06/20/2013 11:36 AM, Bobby Holley wrote:> I think we could pretty easily
promote the typedefs, which will
> get used anyway because they're easier
I think that's debatable. The typedefs are (negligibly) easier to *type*. But
they are not easier to understand. Extra abstraction layers obfus
Hi list,
I have been poking Gaia people around me. Here is a summary of what I
discuss with them, and where our concerns should focus to help them, as well
as any other application developer which want to target low-memory devices.
First of all, B2G is currently focused on the next release,
On Thursday, May 30, 2013 3:23:50 AM UTC+2, Nicolas Pierron wrote:
> I think the recent trouble was mostly that we got multiple regressions in
> the one range of commits.
True and that is also the reason I want to re-empower people again when that
happens. People shouldn't be afraid to backout r
On 05/29/2013 06:09 AM, Hannes Verschore wrote:
My proposal would be something like:
---
Revisions causing regressions on the major benchmarks (Sunspider, Octane,
Kraken) are not allowed at all.
Except: if the regressions are l
10 matches
Mail list logo
