WebSocket Pepper API: C++ bindings implementation.

ppapi/cpp/completion_callback.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 PPAPI_CPP_COMPLETION_CALLBACK_H_
 #define PPAPI_CPP_COMPLETION_CALLBACK_H_
 
 #include "ppapi/c/pp_completion_callback.h"
 #include "ppapi/c/pp_errors.h"
 #include "ppapi/cpp/logging.h"
@@ skipping 161 matching lines @@
 /// creates/destroys the factory. With this restriction, it is safe to create
 /// the <code>CompletionCallbackFactory</code> on the main thread, create
 /// callbacks from any thread and pass them to CallOnMainThread().
 ///
 /// <strong>Example: </strong>
 ///
 /// @code
 ///
 ///   class MyHandler {
 ///    public:
-///     MyHandler() : factory_(this), offset_(0) {
+///     MyHandler()
+///         : factory_(PP_ALLOW_THIS_IN_INITIALIZER_LIST(this)), offset_(0) {

[dmichael (off chromium), 2011/12/09 23:05:26]

Actually, this macro is really just a way around a warning on the Windows
compiler. Maybe leave it alone, but note below that some compilers may warn
about using "this" in an initializer list, and that PP_ALLOW... can be used to
work around the warning?

[Takashi Toyoshima, 2011/12/13 14:08:23]

Done.

 ///     }
 ///
 ///    void ProcessFile(const FileRef& file) {
 ///       CompletionCallback cc = factory_.NewRequiredCallback(
 ///           &MyHandler::DidOpen);
 ///       int32_t rv = fio_.Open(file, PP_FileOpenFlag_Read, cc);
 ///       CHECK(rv == PP_OK_COMPLETIONPENDING);
 ///     }
 ///
 ///    private:
@@ skipping 506 matching lines @@
   CompletionCallbackFactory(const CompletionCallbackFactory&);
   CompletionCallbackFactory& operator=(const CompletionCallbackFactory&);
 
   T* object_;
   BackPointer* back_pointer_;
 };
 
 }  // namespace pp
 
 #endif  // PPAPI_CPP_COMPLETION_CALLBACK_H_