e0c2eeafaa
The macros confuses automatic tooling, Qt Creator fails to identify the tests defined with the special macros used before. The value for readers of defining the macros is not obvious either. Macros can sometime make code more compact and therefore quicker to overview. However they also increases ambiguity of the code and the reader will have to look up their definition to know what they do. In this case I argue that the slight decrease in code size does not outweigh the cost of lost tooling support. Bug: None Change-Id: Ic496fbe1fefdc5acd3f50ec99e2c804bb6065c3d Reviewed-on: https://webrtc-review.googlesource.com/33540 Commit-Queue: Sebastian Jansson <srte@webrtc.org> Reviewed-by: Magnus Jedvert <magjed@webrtc.org> Cr-Commit-Position: refs/heads/master@{#21503}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct