Rename LOG() to LOG_INFO()

Rename LOG() to LOG_INFO()

The current macro name conflicts with a macro from the chromium base/
library. This conflict makes it very difficult to include headers from
both Blink, and Chromium, since wtf/Assertions.h is included from just
about anywhere in Blink.

We should switch to using Chromium's logging mechanisms. But until we
do this avoids conflicts between defines.

Moved from: https://bugs.webkit.org/show_bug.cgi?id=101825

R=eseidel,jamesr

[eseidel, 2013-04-04 14:36:23]

On 2013/04/04 14:12:18, danakj wrote:

I'm OK with this idea.  Do you have a proposal for moving more directly to
Chromium logging? or is this just scratching an old itch?

[danakj, 2013-04-04 14:38:48]

On 2013/04/04 14:36:23, Eric Seidel (Google) wrote:
> On 2013/04/04 14:12:18, danakj wrote:
> 
> I'm OK with this idea.  Do you have a proposal for moving more directly to
> Chromium logging? or is this just scratching an old itch?

It's scratching an itch but also I think it is important in general. We've had
to do some hoop-jumping to include chromium headers like gfx types in WebKit to
avoid this collision, and if we start trying to include more chromium headers
from blink to use chromium types, this conflict is going to cause us pain. IMO
the sooner it goes, the easier it will be to think about including chromium
base/ or ui/gfx/ or whatever else headers.

[eseidel, 2013-04-05 04:03:39]

It's possible to argue either way as to which LOG should change, but in the
intrest of expediency, it seems OK for Blink to be the one changing here.  This
is slightly lame, but I understand the goal.

[eseidel, 2013-04-05 04:03:52]

lgtm

[abarth-chromium, 2013-04-05 04:05:19]

There are some hacks around #undef LOG that we should unwind once this patch
lands.