On Fri, Jan 9, 2015 at 1:16 PM, Joshua Cranmer 🐧
wrote:
> * Range-based for loops
>
BTW, do we have any plan to make nsTArray support range-based for loops?
- Xidorn
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.or
On 1/8/15 9:16 PM, Joshua Cranmer 🐧 wrote:
* Forward declaration of enums
YES!!! This is actually pretty useful for Web IDL enums, since it means
you don't have to include the binding header in your implementation
header just to get the enum.
-Boris
On 1/8/2015 9:16 PM, Joshua Cranmer 🐧 wrote:
On 1/6/2015 3:33 PM, Ehsan Akhgari wrote:
I just landed bug to remove support for building with Visual C++ 2012 as
per the previous dev-platform thread.
Trevor Saunders has just landed the patch to de-support gcc 4.4 and 4.5
on mozilla-inbound, and
The root cause of this cpu spinning issue should due to Socket transport
service thread lack of an error handle mechanism when system error happened in
nsSocketTransportService::DoPollIteration() -> PR_Poll() -> Poll/Select, I have
opened a new bug in Mozilla bugzilla, can anyone help to take a
On 1/6/2015 3:33 PM, Ehsan Akhgari wrote:
I just landed bug to remove support for building with Visual C++ 2012 as
per the previous dev-platform thread.
Trevor Saunders has just landed the patch to de-support gcc 4.4 and 4.5
on mozilla-inbound, and it should move to mozilla-central shortly. I
Bug 1073003, which enables warnings-as-errors on B2G,
landed today.
What this gives us:
- In B2G-only code, the compiler now enforces that we
keep the code warning-free. This is useful because
warnings can often point out legitimate problems in
the code.
- In cross-platform code,
On 1/8/2015 11:56 AM, Joshua Cranmer 🐧 wrote:
In practice, if you're building infrequently (say, provisioning a VM for
Windows or Linux for occasional builds, not primary development), then 4
cores and 4GB of RAM appear to suffice (I've used 4GB for a Linux VM on
my laptop and 8GB for a Windows V
On 1/8/2015 10:05 AM, Mike Hoye wrote:
I'm revisiting our docs in light of this to figure out what our real
minimum hardware/ram/disk requirements are. The temptation to start
adding "If you try to build Firefox with 2 gigs of RAM, you're gonna
have a bad time" memes to the docs is severe.
On
On 2015-01-08 12:15 AM, Botond Ballo wrote:
Building Firefox*for* Windows XP (and running it on Windows XP) is
unaffected.
Building Firefox*on* Windows XP, however, is - I believe - no longer
supported, and in fact hasn't been since we bumped the minimum required
MSVC version to 2012, since
9 matches
Mail list logo
