aboutsummaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorkenton@google.com <kenton@google.com@630680e5-0e50-0410-840e-4b1c322b438d>2009-04-15 19:50:54 +0000
committerkenton@google.com <kenton@google.com@630680e5-0e50-0410-840e-4b1c322b438d>2009-04-15 19:50:54 +0000
commitf663b1602d2675b1ab91d76dd739070d34e01291 (patch)
tree04bc78516c9539b65bd4c74cc6ff31a544ee89bf /CHANGES.txt
parent90bdae226eecf5a97fc7b86078baf055f0702871 (diff)
downloadprotobuf-f663b1602d2675b1ab91d76dd739070d34e01291.tar.gz
protobuf-f663b1602d2675b1ab91d76dd739070d34e01291.tar.bz2
protobuf-f663b1602d2675b1ab91d76dd739070d34e01291.zip
Adds a flag to protoc called --error_format which specifies what
convention to use when printing errors. Default is GCC, but Microsoft Visual Studio is another option. This allows errors to be clickable in the MSVS error log.
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt5
1 files changed, 5 insertions, 0 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index 2a86a63c..94fe94e1 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -9,6 +9,11 @@
be normally except without a tag before each value (thus, they are
tightly "packed").
+ protoc
+ * --error_format=msvs option causes errors to be printed in Visual Studio
+ format, which should allow them to be clicked on in the build log to go
+ directly to the error location.
+
C++
* UnknownFieldSet now supports STL-like iteration.
* Message interface has method ParseFromBoundedZeroCopyStream() which parses