Rename BASE_API to BASE_EXPORT.

base/message_pump_win.h

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef BASE_MESSAGE_PUMP_WIN_H_
 #define BASE_MESSAGE_PUMP_WIN_H_
 #pragma once
 
 #include <windows.h>
 
 #include <list>
 
-#include "base/base_api.h"
+#include "base/base_export.h"
 #include "base/basictypes.h"
 #include "base/message_pump.h"
 #include "base/observer_list.h"
 #include "base/time.h"
 #include "base/win/scoped_handle.h"
 
 namespace base {
 
 // MessagePumpWin serves as the base for specialized versions of the MessagePump
 // for Windows. It provides basic functionality like handling of observers and
 // controlling the lifetime of the message pump.
-class BASE_API MessagePumpWin : public MessagePump {
+class BASE_EXPORT MessagePumpWin : public MessagePump {
  public:
   // An Observer is an object that receives global notifications from the
   // UI MessageLoop.
   //
   // NOTE: An Observer implementation should be extremely fast!
   //
-  class BASE_API Observer {
+  class BASE_EXPORT Observer {
    public:
     virtual ~Observer() {}
 
     // This method is called before processing a message.
     // The message may be undefined in which case msg.message is 0
     virtual void WillProcessMessage(const MSG& msg) = 0;
 
     // This method is called when control returns from processing a UI message.
     // The message may be undefined in which case msg.message is 0
     virtual void DidProcessMessage(const MSG& msg) = 0;
   };
 
   // Dispatcher is used during a nested invocation of Run to dispatch events.
   // If Run is invoked with a non-NULL Dispatcher, MessageLoop does not
   // dispatch events (or invoke TranslateMessage), rather every message is
   // passed to Dispatcher's Dispatch method for dispatch. It is up to the
   // Dispatcher to dispatch, or not, the event.
   //
   // The nested loop is exited by either posting a quit, or returning false
   // from Dispatch.
-  class BASE_API Dispatcher {
+  class BASE_EXPORT Dispatcher {
    public:
     virtual ~Dispatcher() {}
     // Dispatches the event. If true is returned processing continues as
     // normal. If false is returned, the nested loop exits immediately.
     virtual bool Dispatch(const MSG& msg) = 0;
   };
 
   MessagePumpWin() : have_work_(0), state_(NULL) {}
   virtual ~MessagePumpWin() {}
 
@@ skipping 86 matching lines @@
 // kMsgHaveWork messages.  As a result, care is taken to do some peeking in
 // between the posting of each kMsgHaveWork message (i.e., after kMsgHaveWork
 // is peeked, and before a replacement kMsgHaveWork is posted).
 //
 // NOTE: Although it may seem odd that messages are used to start and stop this
 // flow (as opposed to signaling objects, etc.), it should be understood that
 // the native message pump will *only* respond to messages.  As a result, it is
 // an excellent choice.  It is also helpful that the starter messages that are
 // placed in the queue when new task arrive also awakens DoRunLoop.
 //
-class BASE_API MessagePumpForUI : public MessagePumpWin {
+class BASE_EXPORT MessagePumpForUI : public MessagePumpWin {
  public:
   // The application-defined code passed to the hook procedure.
   static const int kMessageFilterCode = 0x5001;
 
   MessagePumpForUI();
   virtual ~MessagePumpForUI();
 
   // MessagePump methods:
   virtual void ScheduleWork();
   virtual void ScheduleDelayedWork(const TimeTicks& delayed_work_time);
@@ skipping 18 matching lines @@
   // A hidden message-only window.
   HWND message_hwnd_;
 };
 
 //-----------------------------------------------------------------------------
 // MessagePumpForIO extends MessagePumpWin with methods that are particular to a
 // MessageLoop instantiated with TYPE_IO. This version of MessagePump does not
 // deal with Windows mesagges, and instead has a Run loop based on Completion
 // Ports so it is better suited for IO operations.
 //
-class BASE_API MessagePumpForIO : public MessagePumpWin {
+class BASE_EXPORT MessagePumpForIO : public MessagePumpWin {
  public:
   struct IOContext;
 
   // Clients interested in receiving OS notifications when asynchronous IO
   // operations complete should implement this interface and register themselves
   // with the message pump.
   //
   // Typical use #1:
   //   // Use only when there are no user's buffers involved on the actual IO,
   //   // so that all the cleanup can be done by the message pump.
@@ skipping 151 matching lines @@
   // This list will be empty almost always. It stores IO completions that have
   // not been delivered yet because somebody was doing cleanup.
   std::list<IOItem> completed_io_;
 
   ObserverList<IOObserver> io_observers_;
 };
 
 }  // namespace base
 
 #endif  // BASE_MESSAGE_PUMP_WIN_H_