diff options
| author | tsepez@chromium.org <tsepez@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-03-17 18:20:52 +0000 |
|---|---|---|
| committer | tsepez@chromium.org <tsepez@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-03-17 18:20:52 +0000 |
| commit | e503a12601fee9e142e37a630f3db9b758499c82 (patch) | |
| tree | 7aa599b0890395b715ff2ab292dde9a2f0b10db6 /ipc/ipc_message_macros.h | |
| parent | 5e3ebf12585ed50e2955d21a6276669f5e3a0e4e (diff) | |
| download | chromium_src-e503a12601fee9e142e37a630f3db9b758499c82.zip chromium_src-e503a12601fee9e142e37a630f3db9b758499c82.tar.gz chromium_src-e503a12601fee9e142e37a630f3db9b758499c82.tar.bz2 | |
Creates the ipclist utility that chrome security team has wanted to dump
the known IPC messages. Going forward, this should help identify new messages
between versions of chrome so that they may be given extra scrutiny for
potential badness.
under the common_message_generator.h umbrella.
Review URL: http://codereview.chromium.org/6646005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78564 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ipc/ipc_message_macros.h')
| -rw-r--r-- | ipc/ipc_message_macros.h | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/ipc/ipc_message_macros.h b/ipc/ipc_message_macros.h index bdc5acc..0320aaa 100644 --- a/ipc/ipc_message_macros.h +++ b/ipc/ipc_message_macros.h @@ -138,11 +138,16 @@ // There's also IPC_STRUCT_TRAITS_PARENT, which is used to register a parent // class (whose own traits are already defined). Note that // IPC_STRUCT_TRAITS_MEMBER() and IPC_STRUCT_TRAITS_PARENT are only permitted -// inside matching calls to IPC_STRUCT_TRAITS_BEGIN() / IPC_STRUCT_TRAITS_END(). +// inside matching calls to IPC_STRUCT_TRAITS_BEGIN() / +// IPC_STRUCT_TRAITS_END(). // // Enum types are registered with a single IPC_ENUM_TRAITS() macro. There // is no need to enumerate each value to the IPC mechanism. // +// Do not place semicolons following these IPC_ macro invocations. There +// is no reason to expect that their expansion corresponds one-to-one with +// C++ statements. +// // Once the types have been declared / registered, message definitions follow. // "Sync" messages are just synchronous calls, the Send() call doesn't return // until a reply comes back. Input parameters are first (const TYPE&), and |