On Tue, Dec 2, 2008 at 5:54 PM, Erik Kay <[EMAIL PROTECTED]> wrote:

> It would be nice to remove ATL/WTL dependencies from Chromium so that
> people can build it with Visual C++ Express.


According to various webpages whose instructions I have not personally
tested (e.g. http://www.codeproject.com/KB/wtl/WTLExpress.aspx ), this is
already possible with a couple of extremely minor tweaks.  If we cared, we
could probably provide a script to make these tweaks.  (Personally, I don't
care.  The Mac/Linux ports and tryserver cover most of the cases where I
think a contributor without a paid version of Visual Studio would be willing
and likely to make contributions.  I don't see huge demand for VS Express
from people doing anything more than tire-kicking.)

I am opposed to removing ATL and WTL.  Ben and I have never agreed on this
and probably will continue to disagree.  There are a number of cases where
WTL makes tricky-to-get-right code noticeably simpler and more readable, and
I have objected to (and been overruled on) cases where we've removed it and
made our code longer and hairier.  There were a number of message-forwarding
problems in our code long ago that never would have occurred if we'd just
used WTL properly instead of being stubborn and trying to write our own
code.

I am not necessarily opposed to replacing WTL with a set of
equally-expressive macros of our own, but writing these macros and catching
the edge cases is, depending on the case, somewhere between tedious and
tricky.  And when a perfectly good library someone else wrote already exists
and is already in our code, I don't understand the motivation.

PK

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Chromium-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to