Re: mozilla::Atomic considered harmful

I've got some outside experience with std::atomic so make of it what you will :) How often are you touching atomic variables directly? In my experience with a similar thread safe inline ref count and smart pointer system to Mozilla's (using std::atomic for the ref count), there's been no confusion

Re: Using C++0x auto

On Mon, Jul 22, 2013 at 12:46 PM, Benjamin Smedberg wrote: > On 7/22/2013 3:01 PM, Rob Arnold wrote: > >> >> Wouldn't disallowing this implicit conversion break code which does >> >>void UseFoo(nsIFoo* foo); >> >>nsCOMPtr foo; >>Us

Re: Using C++0x auto

On Sun, Jul 21, 2013 at 11:59 PM, Justin Lebar wrote: > > It seems really dangerous that there is an implicit conversion from a > strong > > ref ptr to a weak pointer. With C++11, you can thankfully require this > > conversion to be explicit which should alleviate your concern. > > Wouldn't disall

Re: Using C++0x auto

On Sun, Jul 21, 2013 at 10:39 PM, Justin Lebar wrote: > AIUI the new constructor would be something like > > nsRefPtr(nsRefPtr&& aOther) > > where "&&" means "r-value", which means "temporary", so "moveable". > Yes, this is why you want to be careful when returning them. The rules should be mor

Re: Running mousemove events from the refresh driver

On Tue, Feb 12, 2013 at 7:57 PM, Robert O'Callahan wrote: > On Wed, Feb 13, 2013 at 4:45 PM, Rob Arnold wrote: > >> Would you want to predict the mouse location based on past events when >> you dispatch the synthetic event? I guess it depends on how frequently you >&g