On 10/1/2013 4:51 PM, Botond Ballo wrote:
I'm also interested in seeing proposals for standardization of more
complex attributes that we have static analysis results for--in
particular, the stack class/heap class/etc. annotations, the
must_override analysis, and expanding override/must_override
I'm also interested in seeing proposals for standardization of more
complex attributes that we have static analysis results for--in
particular, the stack class/heap class/etc. annotations, the
must_override analysis, and expanding override/must_override to refer to
nonvirtual as well as
I just did a no-op ./mach build binaries on my debug build on a Mac, and
it took about 28 seconds.
$ time ./mach build binaries
0:01.96 /usr/bin/make -j8 -s binaries
0:12.19 From ./dist/public: Kept 0 existing; Added/updated 0; Removed
0 files and 0 directories.
0:12.22 From ./dist/sdk:
On 2013-10-02 11:38 AM, Botond Ballo wrote:
I'm also interested in seeing proposals for standardization of more
complex attributes that we have static analysis results for--in
particular, the stack class/heap class/etc. annotations, the
must_override analysis, and expanding
So, after writing about a bunch of things that _won't_ be in C++14,
let me summarize what _will_ be. Here are the highlights:
* Return type deduction
In C++11, we have decltype() and late-specified return types
(return types written after the argument list so they can
mention
8.8s here!
~1.5 is startup and checking the build backend is up to date (lots of stats)
~1.5s is processing install manifests.
Rest is make processing.
The fact that your machine spent ~20s doing install manifest processing
tells me:
a) Your directory tree wasn't cached (try running again)
this works great for me.. touching network/protocol/http/nsHttpChannel.cpp
and rebuilding with mach build binaries runs in 26 seconds compared to 61
with just mach build, and I see the same ~35 second savings when doing it
on a total nop build (39 vs 5). awesome.
-P
On Tue, Oct 1, 2013 at 9:17
In addition to the C++14 standard, the Committee is working on a
number of follow-up documents called Technical Specifications (TS),
which carry less weight than the standard, but indicate an
intention to standardize a new library or language feature in a
future standard:
* Concepts Lite TS
Finally, let me describe the process for submitting proposals
to the committee for new libraries or language features.
First, let me briefly describe the internal organization of
the committee. The committee is subdivided into four
Working Groups: Core, Evolution, Library, and Library
Hmm, I'm not sure what's going on. I ran it again four times in a row
and I got better results, but the timings show that there is a lot fo
difference between the slow and fast cases (no idea why)
$ time ./mach build binaries
0:00.81 /usr/bin/make -j8 -s binaries
0:03.90 From ./dist/public:
I am writing a xul application which records all the network communication
happening inside a browser instance created using browser tag.
I can use http-on-modify-request to track all the requests being made and
modify headers accordingly but I can not differentiate which request is made by
What features do you most use in MXR and DXR?
Over in the recently renamed Web Engineering group, we're working hard to
retire MXR. It hasn't been maintained for a long time, and there's a lot of
duplication between it and DXR, which rests upon a more modern foundation and
has been developing
This is looking awesome and I'm going to attempt to switch my mxr quick
searches over to it. A couple of immediate things that you might want to
think about:
Right now I think mxr updates from mozilla-central faster than daily. I've
used that on a number of occasions to figure out what has broken
- Easy access to hg annotate, as in mxr (could be better than mxr even, by
integrating into the existing view instead of being a separate view).
Assuming I understand you right, we've just added this last week. :-) See the
Blame link at
DXR is looking awesome these days!
I find the call graph information to be wrong some of the time, I have
never been able to tell why. See this query for example:
I love DXR for mozilla-central, and would love it if the UX branch
(https://mxr.mozilla.org/projects-central/source/ux/) was indexed there
as well!
Keep up the great work,
-Mike
On 02/10/2013 3:33 PM, Erik Rose wrote:
What features do you most use in MXR and DXR?
Over in the recently
I've been using DXR (at least when it has been working) since 2011. One
thing I'd like to see should be simple to implement: typing a file name
into the search bar should find that file rather than nothing.
On 10/02/2013 12:33 PM, Erik Rose wrote:
What features do you most use in MXR and DXR?
On 10/2/13 3:33 PM, Erik Rose wrote:
What keeps you off DXR? (What are the MXR things you use constantly? Or the
things which are seldom-used but vital?)
MXR things I use constantly that don't seem to have obvious dxr
counterparts:
* Search on the firefox tree to follow pre-hg blame.
On 02/10/13 21:33 , Erik Rose wrote:
What features do you most use in MXR and DXR?
Over in the recently renamed Web Engineering group, we're working hard to
retire MXR. It hasn't been maintained for a long time, and there's a lot of
duplication between it and DXR, which rests upon a more
Erik Rose wrote:
What features do you most use in MXR and DXR?
Over in the recently renamed Web Engineering group, we're working hard to
retire MXR. It hasn't been maintained for a long time, and there's a lot of
duplication between it and DXR, which rests upon a more modern foundation and
On 13-10-02 2:09 PM, Gijs Kruitbosch wrote:
On 02/10/13 21:33 , Erik Rose wrote:
What features do you most use in MXR and DXR?
Over in the recently renamed Web Engineering group, we're working hard
to retire MXR. It hasn't been maintained for a long time, and there's
a lot of duplication
Could we run with DEBUG on? We'd index strictly more code (I think) and
sometimes I miss debug-only things.
(One day I would love to get Windows-only stuff indexed, but I guess we have to
wait for Clang to work on Windows for that).
Nick
On Thursday, October 3, 2013 8:33:40 AM UTC+13, Erik
On Wed, Oct 2, 2013 at 1:52 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 10/2/13 3:33 PM, Erik Rose wrote:
What keeps you off DXR? (What are the MXR things you use constantly? Or
the things which are seldom-used but vital?)
Things that drive me nuts about mxr when I've tried to use it:
*
I would like better documentation about how to use dxr. I know it's pretty
powerful, but it's always just easier for me to use mxr than to figure out the
right query. One that would be really useful to me is to find all references to
a field of a given class. If dxr's main search page had some
On Wed, Oct 02, 2013 at 11:42:45AM -0400, Ehsan Akhgari wrote:
I just did a no-op ./mach build binaries on my debug build on a Mac,
and it took about 28 seconds.
$ time ./mach build binaries
0:01.96 /usr/bin/make -j8 -s binaries
0:12.19 From ./dist/public: Kept 0 existing; Added/updated
On Wed 02 Oct 2013 12:33:40 PM PDT, Erik Rose wrote:
What features do you most use in MXR and DXR?
Over in the recently renamed Web Engineering group, we're working hard to
retire MXR. It hasn't been maintained for a long time, and there's a lot of
duplication between it and DXR, which
26 matches
Mail list logo
