On Tue, Jan 13, 2009 at 11:56 PM, Ben Goodger (Google) b...@chromium.orgwrote:
It looks like everyone and their dog adds init code to the startup
sequence. This takes the form of first time initialization, command
line switch parsing, etc. Is there any special reason why it's done in
the
I am sure most of you have seen the news by now that Qt is switching
from GPL to LGPL licensing. Does this increase the chances of a Qt
Chrome on Linux instead of GTK or has too much work already been
completed on the Linux GUI?
--~--~-~--~~~---~--~~
Chromium
On Wed, Jan 14, 2009 at 9:15 AM, andrewg droi...@gmail.com wrote:
I am sure most of you have seen the news by now that Qt is switching
from GPL to LGPL licensing. Does this increase the chances of a Qt
Chrome on Linux instead of GTK or has too much work already been
completed on the Linux
Our CommandLine class is very confusing -- it is not a class for
working with command lines, but in fact a stealth singleton that wraps
the command line used to start the process.
Further, since it came from Windows, it does all this string-munging
and quoting that is not necessary on OS X or
I don't think that it is actually *always* used as a singleton
currently. As Ricardo pointed out, only the default constructor uses
the CommandLine::Data singleton. The other constructors create new
Data objects. This is somewhat moot though if you will be ditching the
Data class. And that
On Wed, Jan 14, 2009 at 6:22 PM, Evan Martin e...@chromium.org wrote:
Our CommandLine class is very confusing -- it is not a class for
working with command lines, but in fact a stealth singleton that wraps
the command line used to start the process.
Further, since it came from Windows, it
the winsock initialization can be removed now that we have EnsureWinSockInit
which should be called by any code that uses winsock. (we may not have
sprinkled that in all of the right places, but you get the idea.)
i really like your idea of documenting startup dependencies, and i agree
that the
