thrift/compiler/cpp
David Reiss cbd4bacc30 Thrift: docstring revamp step 2.
Summary:
It was a bad idea to let doxygen comments become a part of the parse tree.
We now get them a totally different way.  The lexer stashes the docsting
contents in a global, and the parser actions (not the rules) pull it out.
This should prevent doxygen comments from ever causing parse errors.

Blame Rev: 52678, 52732

Reviewed By: mcslee

Test Plan:
Recompiled thrift.
Thrifted a bunch of files and saw no parse errors (or C++ compile errors).
Thrifted DocTest.thrift with dump_docs on.

Revert Plan: ok


git-svn-id: https://svn.apache.org/repos/asf/incubator/thrift/trunk@665201 13f79535-47bb-0310-9956-ffa450edef68
2007-08-14 17:12:33 +00:00
..
src Thrift: docstring revamp step 2. 2007-08-14 17:12:33 +00:00
bootstrap.sh Lots of Ruby code generation improvements 2007-07-06 02:45:25 +00:00
cleanup.sh Various Thrift fixes, including Application Exception support in Ruby, better errror messages across languages, etc. 2007-03-14 02:47:35 +00:00
configure.ac Lots of Ruby code generation improvements 2007-07-06 02:45:25 +00:00
COPYING Some Thrift documentation cleanups 2007-02-28 21:43:54 +00:00
LICENSE Some Thrift documentation cleanups 2007-02-28 21:43:54 +00:00
Makefile.am Thrift: docstring revamp step 2. 2007-08-14 17:12:33 +00:00
README Ruby code gen fixes and some README improvements 2007-03-07 05:46:50 +00:00

Thrift Code Compiler

Author: Mark Slee (mcslee@facebook.com)
Last Modified: 2007-Mar-06

Thrift is distributed under the Thrift open source software license.
Please see the included LICENSE file.

Thrift Code Compiler
====================

This compiler takes thrift files as input and generates output code across
various programming languages. To build and install it, do this:

  ./bootstrap.sh
  ./configure
  make
  sudo make install

It requires some form of LEX and YACC to be installed, which should be
picked up by autoconf.

Not much else to report here. You'll have to look at the code to get your
questions answered. Or just run the executable after you build and take
a look at the usage message.