summaryrefslogtreecommitdiff
path: root/upb/handlers.h
diff options
context:
space:
mode:
authorJosh Haberman <jhaberman@gmail.com>2015-07-07 18:46:14 -0700
committerJosh Haberman <jhaberman@gmail.com>2015-07-07 18:46:14 -0700
commit49dab06e03c16691c4dab1ba012fe8488089a590 (patch)
tree209f0749cbba6db8c9f0bf1094e6b5b5cd5190a0 /upb/handlers.h
parent6d9a9c727fd966acec7340aeabd5bf4039c6d929 (diff)
Brought into compliance with Google open-source policies.
- removed myself from Author headers in source files. - removed copyright notices from source file headers. - added CONTRIBUTING.md
Diffstat (limited to 'upb/handlers.h')
-rw-r--r--upb/handlers.h35
1 files changed, 16 insertions, 19 deletions
diff --git a/upb/handlers.h b/upb/handlers.h
index 229d808..8925d4f 100644
--- a/upb/handlers.h
+++ b/upb/handlers.h
@@ -1,23 +1,20 @@
/*
- * upb - a minimalist implementation of protocol buffers.
- *
- * Copyright (c) 2010-2012 Google Inc. See LICENSE for details.
- * Author: Josh Haberman <jhaberman@gmail.com>
- *
- * A upb_handlers is like a virtual table for a upb_msgdef. Each field of the
- * message can have associated functions that will be called when we are
- * parsing or visiting a stream of data. This is similar to how handlers work
- * in SAX (the Simple API for XML).
- *
- * The handlers have no idea where the data is coming from, so a single set of
- * handlers could be used with two completely different data sources (for
- * example, a parser and a visitor over in-memory objects). This decoupling is
- * the most important feature of upb, because it allows parsers and serializers
- * to be highly reusable.
- *
- * This is a mixed C/C++ interface that offers a full API to both languages.
- * See the top-level README for more information.
- */
+** upb::Handlers (upb_handlers)
+**
+** A upb_handlers is like a virtual table for a upb_msgdef. Each field of the
+** message can have associated functions that will be called when we are
+** parsing or visiting a stream of data. This is similar to how handlers work
+** in SAX (the Simple API for XML).
+**
+** The handlers have no idea where the data is coming from, so a single set of
+** handlers could be used with two completely different data sources (for
+** example, a parser and a visitor over in-memory objects). This decoupling is
+** the most important feature of upb, because it allows parsers and serializers
+** to be highly reusable.
+**
+** This is a mixed C/C++ interface that offers a full API to both languages.
+** See the top-level README for more information.
+*/
#ifndef UPB_HANDLERS_H
#define UPB_HANDLERS_H
generated by cgit on debian on lair
contact matthew@masot.net with questions or feedback