jieba-rb 5.0.0

data/ext/cppjieba/README.md

@@ -0,0 +1,285 @@
+# CppJieba [English](README_EN.md)
+
+[![Build Status](https://travis-ci.org/yanyiwu/cppjieba.png?branch=master)](https://travis-ci.org/yanyiwu/cppjieba) 
+[![Author](https://img.shields.io/badge/author-@yanyiwu-blue.svg?style=flat)](http://yanyiwu.com/) 
+[![Platform](https://img.shields.io/badge/platform-Linux,%20OS%20X,%20Windows-green.svg?style=flat)](https://github.com/yanyiwu/cppjieba)
+[![Performance](https://img.shields.io/badge/performance-excellent-brightgreen.svg?style=flat)](http://yanyiwu.com/work/2015/06/14/jieba-series-performance-test.html) 
+[![License](https://img.shields.io/badge/license-MIT-yellow.svg?style=flat)](http://yanyiwu.mit-license.org)
+[![Build status](https://ci.appveyor.com/api/projects/status/wl30fjnm2rhft6ta/branch/master?svg=true)](https://ci.appveyor.com/project/yanyiwu/cppjieba/branch/master)
+
+[![logo](http://7viirv.com1.z0.glb.clouddn.com/CppJiebaLogo-v1.png)](https://github.com/yanyiwu/cppjieba)
+
+## 简介
+
+CppJieba是"结巴(Jieba)"中文分词的C++版本
+
+## 特性
+
++ 源代码都写进头文件`include/cppjieba/*.hpp`里，`include`即可使用。
++ 支持`utf8`编码。
++ 项目自带较为完善的单元测试，核心功能中文分词(utf8)的稳定性接受过线上环境检验。
++ 支持载自定义用户词典，多路径时支持分隔符'|'或者';'分隔。
++ 支持 `Linux` , `Mac OSX`, `Windows` 操作系统。
+
+## 用法
+
+### 依赖软件
+
+* `g++ (version >= 4.1 is recommended) or clang++`;
+* `cmake (version >= 2.6 is recommended)`;
+
+### 下载和编译
+
+```sh
+git clone --depth=10 --branch=master git://github.com/yanyiwu/cppjieba.git
+cd cppjieba
+mkdir build
+cd build
+cmake ..
+make
+```
+
+有兴趣的可以跑跑测试(可选):
+
+```
+make test
+```
+
+## Demo
+
+```
+./demo
+```
+
+结果示例：
+
+```
+[demo] Cut With HMM
+他/来到/了/网易/杭研/大厦
+[demo] Cut Without HMM
+他/来到/了/网易/杭/研/大厦
+我来到北京清华大学
+[demo] CutAll
+我/来到/北京/清华/清华大学/华大/大学
+小明硕士毕业于中国科学院计算所，后在日本京都大学深造
+[demo] CutForSearch
+小明/硕士/毕业/于/中国/科学/学院/科学院/中国科学院/计算/计算所/，/后/在/日本/京都/大学/日本京都大学/深造
+[demo] Insert User Word
+男默/女泪
+男默女泪
+[demo] CutForSearch Word With Offset
+[{"word": "小明", "offset": 0}, {"word": "硕士", "offset": 6}, {"word": "毕业", "offset": 12}, {"word": "于", "offset": 18}, {"word": "中国", "offset": 21}, {"word": "科学", "offset": 27}, {"word": "学院", "offset": 30}, {"word": "科学院", "offset": 27}, {"word": "中国科学院", "offset": 21}, {"word": "计算", "offset": 36}, {"word": "计算所", "offset": 36}, {"word": "，", "offset": 45}, {"word": "后", "offset": 48}, {"word": "在", "offset": 51}, {"word": "日本", "offset": 54}, {"word": "京都", "offset": 60}, {"word": "大学", "offset": 66}, {"word": "日本京都大学", "offset": 54}, {"word": "深造", "offset": 72}]
+[demo] Tagging
+我是拖拉机学院手扶拖拉机专业的。不用多久，我就会升职加薪，当上CEO，走上人生巅峰。
+[我:r, 是:v, 拖拉机:n, 学院:n, 手扶拖拉机:n, 专业:n, 的:uj, 。:x, 不用:v, 多久:m, ，:x, 我:r, 就:d, 会:v, 升职:v, 加薪:nr, ，:x, 当上:t, CEO:eng, ，:x, 走上:v, 人生:n, 巅峰:n, 。:x]
+[demo] Keyword Extraction
+我是拖拉机学院手扶拖拉机专业的。不用多久，我就会升职加薪，当上CEO，走上人生巅峰。
+[{"word": "CEO", "offset": [93], "weight": 11.7392}, {"word": "升职", "offset": [72], "weight": 10.8562}, {"word": "加薪", "offset": [78], "weight": 10.6426}, {"word": "手扶拖拉机", "offset": [21], "weight": 10.0089}, {"word": "巅峰", "offset": [111], "weight": 9.49396}]
+```
+
+详细请看 `test/demo.cpp`.
+
+### 分词结果示例
+
+**MPSegment**
+
+Output:
+```
+我来到北京清华大学
+我/来到/北京/清华大学
+
+他来到了网易杭研大厦
+他/来到/了/网易/杭/研/大厦
+
+小明硕士毕业于中国科学院计算所，后在日本京都大学深造
+小/明/硕士/毕业/于/中国科学院/计算所/，/后/在/日本京都大学/深造
+
+```
+
+**HMMSegment**
+
+```
+我来到北京清华大学
+我来/到/北京/清华大学
+
+他来到了网易杭研大厦
+他来/到/了/网易/杭/研大厦
+
+小明硕士毕业于中国科学院计算所，后在日本京都大学深造
+小明/硕士/毕业于/中国/科学院/计算所/，/后/在/日/本/京/都/大/学/深/造
+
+```
+
+**MixSegment**
+
+```
+我来到北京清华大学
+我/来到/北京/清华大学
+
+他来到了网易杭研大厦
+他/来到/了/网易/杭研/大厦
+
+小明硕士毕业于中国科学院计算所，后在日本京都大学深造
+小明/硕士/毕业/于/中国科学院/计算所/，/后/在/日本京都大学/深造
+
+```
+
+**FullSegment**
+
+```
+我来到北京清华大学
+我/来到/北京/清华/清华大学/华大/大学
+
+他来到了网易杭研大厦
+他/来到/了/网易/杭/研/大厦
+
+小明硕士毕业于中国科学院计算所，后在日本京都大学深造
+小/明/硕士/毕业/于/中国/中国科学院/科学/科学院/学院/计算/计算所/，/后/在/日本/日本京都大学/京都/京都大学/大学/深造
+
+```
+
+**QuerySegment**
+
+```
+我来到北京清华大学
+我/来到/北京/清华/清华大学/华大/大学
+
+他来到了网易杭研大厦
+他/来到/了/网易/杭研/大厦
+
+小明硕士毕业于中国科学院计算所，后在日本京都大学深造
+小明/硕士/毕业/于/中国/中国科学院/科学/科学院/学院/计算所/，/后/在/中国/中国科学院/科学/科学院/学院/日本/日本京都大学/京都/京都大学/大学/深造
+
+```
+
+以上依次是MP,HMM,Mix三种方法的效果。  
+
+可以看出效果最好的是Mix，也就是融合MP和HMM的切词算法。即可以准确切出词典已有的词，又可以切出像"杭研"这样的未登录词。
+
+Full方法切出所有字典里的词语。
+
+Query方法先使用Mix方法切词，对于切出来的较长的词再使用Full方法。
+
+### 自定义用户词典
+
+自定义词典示例请看`dict/user.dict.utf8`。
+
+没有使用自定义用户词典时的结果:
+
+```
+令狐冲/是/云/计算/行业/的/专家
+```
+
+使用自定义用户词典时的结果:
+
+```
+令狐冲/是/云计算/行业/的/专家
+```
+
+### 关键词抽取
+
+```
+我是拖拉机学院手扶拖拉机专业的。不用多久，我就会升职加薪，当上CEO，走上人生巅峰。
+["CEO:11.7392", "升职:10.8562", "加薪:10.6426", "手扶拖拉机:10.0089", "巅峰:9.49396"]
+```
+
+详细请见 `test/demo.cpp`.
+
+### 词性标注
+
+```
+我是蓝翔技工拖拉机学院手扶拖拉机专业的。不用多久，我就会升职加薪，当上总经理，出任CEO，迎娶白富美，走上人生巅峰。
+["我:r", "是:v", "拖拉机:n", "学院:n", "手扶拖拉机:n", "专业:n", "的:uj", "。:x", "不用:v", "多久:m", "，:x", "我:r", "就:d", "会:v", "升职:v", "加薪:nr", "，:x", "当上:t", "CEO:eng", "，:x", "走上:v", "人生:n", "巅峰:n", "。:x"]
+```
+
+详细请看 `test/demo.cpp`.
+
+支持自定义词性。
+比如在(`dict/user.dict.utf8`)增加一行
+
+```
+蓝翔 nz
+```
+
+结果如下：
+
+```
+["我:r", "是:v", "蓝翔:nz", "技工:n", "拖拉机:n", "学院:n", "手扶拖拉机:n", "专业:n", "的:uj", "。:x", "不用:v", "多久:m", "，:x", "我:r", "就:d", "会:v", "升职:v", "加薪:nr", "，:x", "当:t", "上:f", "总经理:n", "，:x", "出任:v", "CEO:eng", "，:x", "迎娶:v", "白富美:x", "，:x", "走上:v", "人生:n", "巅峰:n", "。:x"]
+```
+
+## 其它词典资料分享
+
++ [dict.367W.utf8] iLife(562193561 at qq.com)
+
+## 应用
+
++ [GoJieba] go语言版本的结巴中文分词。
++ [NodeJieba] Node.js 版本的结巴中文分词。
++ [simhash] 中文文档的的相似度计算
++ [exjieba] Erlang 版本的结巴中文分词。
++ [jiebaR] R语言版本的结巴中文分词。
++ [cjieba] C语言版本的结巴分词。
++ [jieba_rb] Ruby 版本的结巴分词。
++ [iosjieba] iOS 版本的结巴分词。
++ [SqlJieba] MySQL 全文索引的结巴中文分词插件。
++ [pg_jieba] PostgreSQL 数据库的分词插件。
++ [gitbook-plugin-search-pro] 支持中文搜索的 gitbook 插件。
++ [ngx_http_cppjieba_module] Nginx 分词插件。
++ [cppjiebapy] 由 [jannson] 开发的供 python 模块调用的项目 [cppjiebapy], 相关讨论 [cppjiebapy_discussion] .
++ [KeywordServer] 50行搭建一个中文关键词抽取服务。
++ [cppjieba-server] CppJieba HTTP 服务器。
+
+## 线上演示
+
+[Web-Demo](http://cppjieba-webdemo.herokuapp.com/)
+(建议使用chrome打开)
+
+## 性能评测
+
+[Jieba中文分词系列性能评测]
+
+## 客服
+
++ Email: `i@yanyiwu.com`
++ QQ: 64162451
++ WeChat: ![image](http://7viirv.com1.z0.glb.clouddn.com/5a7d1b5c0d_yanyiwu_personal_qrcodes.jpg)
+
+## 鸣谢
+
+"结巴"中文分词作者: [SunJunyi](https://github.com/fxsjy)
+
+## 许可证
+
+[MIT](http://yanyiwu.mit-license.org)
+
+## 作者
+
+- [yanyiwu](yanyiwu.com)
+- [aholic](https://github.com/aholic)
+
+[GoJieba]:https://github.com/yanyiwu/gojieba
+[CppJieba]:https://github.com/yanyiwu/cppjieba
+[jannson]:https://github.com/jannson
+[cppjiebapy]:https://github.com/jannson/cppjiebapy
+[cppjiebapy_discussion]:https://github.com/yanyiwu/cppjieba/issues/1
+[NodeJieba]:https://github.com/yanyiwu/nodejieba
+[jiebaR]:https://github.com/qinwf/jiebaR
+[simhash]:https://github.com/yanyiwu/simhash
+[代码详解]:https://github.com/yanyiwu/cppjieba/wiki/CppJieba%E4%BB%A3%E7%A0%81%E8%AF%A6%E8%A7%A3
+[issue25]:https://github.com/yanyiwu/cppjieba/issues/25
+[exjieba]:https://github.com/falood/exjieba
+[KeywordServer]:https://github.com/yanyiwu/keyword_server
+[ngx_http_cppjieba_module]:https://github.com/yanyiwu/ngx_http_cppjieba_module
+[dict.367W.utf8]:https://github.com/qinwf/BigDict
+[cjieba]:http://github.com/yanyiwu/cjieba
+[jieba_rb]:https://github.com/altkatz/jieba_rb
+[iosjieba]:https://github.com/yanyiwu/iosjieba
+[SqlJieba]:https://github.com/yanyiwu/sqljieba
+[Jieba中文分词系列性能评测]:http://yanyiwu.com/work/2015/06/14/jieba-series-performance-test.html
+[pg_jieba]:https://github.com/jaiminpan/pg_jieba
+[gitbook-plugin-search-pro]:https://plugins.gitbook.com/plugin/search-pro
+[cppjieba-server]:https://github.com/yanyiwu/cppjieba-server
+
+
+[![Bitdeli Badge](https://d2weczhvl823v0.cloudfront.net/yanyiwu/cppjieba/trend.png)](https://bitdeli.com/free "Bitdeli Badge")
+

data/ext/cppjieba/README_EN.md

@@ -0,0 +1,111 @@
+# CppJieba [简体中文](README.md)
+
+[![Build Status](https://travis-ci.org/yanyiwu/cppjieba.png?branch=master)](https://travis-ci.org/yanyiwu/cppjieba) 
+[![Author](https://img.shields.io/badge/author-@yanyiwu-blue.svg?style=flat)](http://yanyiwu.com/) 
+[![Platform](https://img.shields.io/badge/platform-Linux,%20OS%20X,%20Windows-green.svg?style=flat)](https://github.com/yanyiwu/cppjieba)
+[![Performance](https://img.shields.io/badge/performance-excellent-brightgreen.svg?style=flat)](http://yanyiwu.com/work/2015/06/14/jieba-series-performance-test.html) 
+[![License](https://img.shields.io/badge/license-MIT-yellow.svg?style=flat)](http://yanyiwu.mit-license.org)
+[![Build status](https://ci.appveyor.com/api/projects/status/wl30fjnm2rhft6ta/branch/master?svg=true)](https://ci.appveyor.com/project/yanyiwu/cppjieba/branch/master)
+
+[![logo](http://7viirv.com1.z0.glb.clouddn.com/CppJiebaLogo-v1.png)](https://github.com/yanyiwu/cppjieba)
+
+## Introduction
+
+The Jieba Chinese Word Segmentation Implemented By C++ .
+
+## Usage 
+
+### Dependencies
+
++ `g++ (version >= 4.1 is recommended) or clang++`;
++ `cmake (version >= 2.6 is recommended)`;
+
+### Download & Compile
+
+```sh
+git clone --depth=10 --branch=master git://github.com/yanyiwu/cppjieba.git
+cd cppjieba
+mkdir build
+cd build
+cmake ..
+make
+```
+
+### Unit Testing
+
+```
+make test
+```
+
+## Demo
+
+```
+./demo
+```
+
+Output:
+
+```
+[demo] Cut With HMM
+他/来到/了/网易/杭研/大厦
+[demo] Cut Without HMM
+他/来到/了/网易/杭/研/大厦
+我来到北京清华大学
+[demo] CutAll
+我/来到/北京/清华/清华大学/华大/大学
+小明硕士毕业于中国科学院计算所，后在日本京都大学深造
+[demo] CutForSearch
+小明/硕士/毕业/于/中国/科学/学院/科学院/中国科学院/计算/计算所/，/后/在/日本/京都/大学/日本京都大学/深造
+[demo] Insert User Word
+男默/女泪
+男默女泪
+[demo] CutForSearch Word With Offset
+[{"word": "小明", "offset": 0}, {"word": "硕士", "offset": 6}, {"word": "毕业", "offset": 12}, {"word": "于", "offset": 18}, {"word": "中国", "offset": 21}, {"word": "科学", "offset": 27}, {"word": "学院", "offset": 30}, {"word": "科学院", "offset": 27}, {"word": "中国科学院", "offset": 21}, {"word": "计算", "offset": 36}, {"word": "计算所", "offset": 36}, {"word": "，", "offset": 45}, {"word": "后", "offset": 48}, {"word": "在", "offset": 51}, {"word": "日本", "offset": 54}, {"word": "京都", "offset": 60}, {"word": "大学", "offset": 66}, {"word": "日本京都大学", "offset": 54}, {"word": "深造", "offset": 72}]
+[demo] Tagging
+我是拖拉机学院手扶拖拉机专业的。不用多久，我就会升职加薪，当上CEO，走上人生巅峰。
+[我:r, 是:v, 拖拉机:n, 学院:n, 手扶拖拉机:n, 专业:n, 的:uj, 。:x, 不用:v, 多久:m, ，:x, 我:r, 就:d, 会:v, 升职:v, 加薪:nr, ，:x, 当上:t, CEO:eng, ，:x, 走上:v, 人生:n, 巅峰:n, 。:x]
+[demo] Keyword Extraction
+我是拖拉机学院手扶拖拉机专业的。不用多久，我就会升职加薪，当上CEO，走上人生巅峰。
+[{"word": "CEO", "offset": [93], "weight": 11.7392}, {"word": "升职", "offset": [72], "weight": 10.8562}, {"word": "加薪", "offset": [78], "weight": 10.6426}, {"word": "手扶拖拉机", "offset": [21], "weight": 10.0089}, {"word": "巅峰", "offset": [111], "weight": 9.49396}]
+```
+
+Please see details in `test/demo.cpp`.
+
+## Cases
+
++ [GoJieba] 
++ [NodeJieba]
++ [simhash]
++ [exjieba]
++ [jiebaR]
++ [cjieba]
++ [jieba_rb]
++ [iosjieba]
++ [SqlJieba]
++ [pg_jieba]
++ [ngx_http_cppjieba_module]
++ [gitbook-plugin-search-pro]
++ [cppjieba-server]
+
+## Contact
+
++ Email: `i@yanyiwu.com`
++ QQ: 64162451
++ WeChat: ![image](http://7viirv.com1.z0.glb.clouddn.com/5a7d1b5c0d_yanyiwu_personal_qrcodes.jpg)
+
+[GoJieba]:https://github.com/yanyiwu/gojieba
+[CppJieba]:https://github.com/yanyiwu/cppjieba
+[jannson]:https://github.com/jannson
+[cppjiebapy]:https://github.com/jannson/cppjiebapy
+[cppjiebapy_discussion]:https://github.com/yanyiwu/cppjieba/issues/1
+[NodeJieba]:https://github.com/yanyiwu/nodejieba
+[jiebaR]:https://github.com/qinwf/jiebaR
+[simhash]:https://github.com/yanyiwu/simhash
+[exjieba]:https://github.com/falood/exjieba
+[cjieba]:http://github.com/yanyiwu/cjieba
+[jieba_rb]:https://github.com/altkatz/jieba_rb
+[iosjieba]:https://github.com/yanyiwu/iosjieba
+[SqlJieba]:https://github.com/yanyiwu/sqljieba
+[pg_jieba]:https://github.com/jaiminpan/pg_jieba
+[gitbook-plugin-search-pro]:https://plugins.gitbook.com/plugin/search-pro
+[cppjieba-server]:https://github.com/yanyiwu/cppjieba-server

data/ext/cppjieba/appveyor.yml

@@ -0,0 +1,32 @@
+os: Visual Studio 2015
+
+platform: x64
+
+# clone directory
+clone_folder: c:\projects\cppjieba
+
+# scripts to run before build
+before_build:
+  - echo Running cmake...
+  - cd c:\projects\cppjieba
+  - cmake .
+
+build:
+  project: ALL_BUILD.vcxproj # path to Visual Studio solution or project
+
+# scripts to run after build
+after_build:
+  - cd Debug
+  - demo.exe
+  - load_test.exe
+  - cd ..
+  - COPY .\test\Debug\test.run.exe .\test\test.run.exe
+  - cd test
+  - test.run.exe
+  - cd ..
+  - 7z a c:\projects\all.zip * -tzip
+  - cd c:\projects
+
+artifacts:
+  - path: all.zip
+    name: all.zip

data/ext/cppjieba/deps/CMakeLists.txt

@@ -0,0 +1 @@
+ADD_SUBDIRECTORY(gtest)

data/ext/cppjieba/deps/gtest/CMakeLists.txt

@@ -0,0 +1,5 @@
+INCLUDE_DIRECTORIES(./ include)
+ADD_LIBRARY(gtest STATIC src/gtest-all.cc)
+if(NOT MSVC)
+	TARGET_LINK_LIBRARIES(gtest pthread)
+endif()

data/ext/cppjieba/deps/gtest/include/gtest/gtest-death-test.h

@@ -0,0 +1,283 @@
+// Copyright 2005, Google Inc.
+// All rights reserved.
+//
+// Redistribution and use in source and binary forms, with or without
+// modification, are permitted provided that the following conditions are
+// met:
+//
+//     * Redistributions of source code must retain the above copyright
+// notice, this list of conditions and the following disclaimer.
+//     * Redistributions in binary form must reproduce the above
+// copyright notice, this list of conditions and the following disclaimer
+// in the documentation and/or other materials provided with the
+// distribution.
+//     * Neither the name of Google Inc. nor the names of its
+// contributors may be used to endorse or promote products derived from
+// this software without specific prior written permission.
+//
+// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+//
+// Author: wan@google.com (Zhanyong Wan)
+//
+// The Google C++ Testing Framework (Google Test)
+//
+// This header file defines the public API for death tests.  It is
+// #included by gtest.h so a user doesn't need to include this
+// directly.
+
+#ifndef GTEST_INCLUDE_GTEST_GTEST_DEATH_TEST_H_
+#define GTEST_INCLUDE_GTEST_GTEST_DEATH_TEST_H_
+
+#include "gtest/internal/gtest-death-test-internal.h"
+
+namespace testing {
+
+// This flag controls the style of death tests.  Valid values are "threadsafe",
+// meaning that the death test child process will re-execute the test binary
+// from the start, running only a single death test, or "fast",
+// meaning that the child process will execute the test logic immediately
+// after forking.
+GTEST_DECLARE_string_(death_test_style);
+
+#if GTEST_HAS_DEATH_TEST
+
+// The following macros are useful for writing death tests.
+
+// Here's what happens when an ASSERT_DEATH* or EXPECT_DEATH* is
+// executed:
+//
+//   1. It generates a warning if there is more than one active
+//   thread.  This is because it's safe to fork() or clone() only
+//   when there is a single thread.
+//
+//   2. The parent process clone()s a sub-process and runs the death
+//   test in it; the sub-process exits with code 0 at the end of the
+//   death test, if it hasn't exited already.
+//
+//   3. The parent process waits for the sub-process to terminate.
+//
+//   4. The parent process checks the exit code and error message of
+//   the sub-process.
+//
+// Examples:
+//
+//   ASSERT_DEATH(server.SendMessage(56, "Hello"), "Invalid port number");
+//   for (int i = 0; i < 5; i++) {
+//     EXPECT_DEATH(server.ProcessRequest(i),
+//                  "Invalid request .* in ProcessRequest()")
+//         << "Failed to die on request " << i);
+//   }
+//
+//   ASSERT_EXIT(server.ExitNow(), ::testing::ExitedWithCode(0), "Exiting");
+//
+//   bool KilledBySIGHUP(int exit_code) {
+//     return WIFSIGNALED(exit_code) && WTERMSIG(exit_code) == SIGHUP;
+//   }
+//
+//   ASSERT_EXIT(client.HangUpServer(), KilledBySIGHUP, "Hanging up!");
+//
+// On the regular expressions used in death tests:
+//
+//   On POSIX-compliant systems (*nix), we use the <regex.h> library,
+//   which uses the POSIX extended regex syntax.
+//
+//   On other platforms (e.g. Windows), we only support a simple regex
+//   syntax implemented as part of Google Test.  This limited
+//   implementation should be enough most of the time when writing
+//   death tests; though it lacks many features you can find in PCRE
+//   or POSIX extended regex syntax.  For example, we don't support
+//   union ("x|y"), grouping ("(xy)"), brackets ("[xy]"), and
+//   repetition count ("x{5,7}"), among others.
+//
+//   Below is the syntax that we do support.  We chose it to be a
+//   subset of both PCRE and POSIX extended regex, so it's easy to
+//   learn wherever you come from.  In the following: 'A' denotes a
+//   literal character, period (.), or a single \\ escape sequence;
+//   'x' and 'y' denote regular expressions; 'm' and 'n' are for
+//   natural numbers.
+//
+//     c     matches any literal character c
+//     \\d   matches any decimal digit
+//     \\D   matches any character that's not a decimal digit
+//     \\f   matches \f
+//     \\n   matches \n
+//     \\r   matches \r
+//     \\s   matches any ASCII whitespace, including \n
+//     \\S   matches any character that's not a whitespace
+//     \\t   matches \t
+//     \\v   matches \v
+//     \\w   matches any letter, _, or decimal digit
+//     \\W   matches any character that \\w doesn't match
+//     \\c   matches any literal character c, which must be a punctuation
+//     .     matches any single character except \n
+//     A?    matches 0 or 1 occurrences of A
+//     A*    matches 0 or many occurrences of A
+//     A+    matches 1 or many occurrences of A
+//     ^     matches the beginning of a string (not that of each line)
+//     $     matches the end of a string (not that of each line)
+//     xy    matches x followed by y
+//
+//   If you accidentally use PCRE or POSIX extended regex features
+//   not implemented by us, you will get a run-time failure.  In that
+//   case, please try to rewrite your regular expression within the
+//   above syntax.
+//
+//   This implementation is *not* meant to be as highly tuned or robust
+//   as a compiled regex library, but should perform well enough for a
+//   death test, which already incurs significant overhead by launching
+//   a child process.
+//
+// Known caveats:
+//
+//   A "threadsafe" style death test obtains the path to the test
+//   program from argv[0] and re-executes it in the sub-process.  For
+//   simplicity, the current implementation doesn't search the PATH
+//   when launching the sub-process.  This means that the user must
+//   invoke the test program via a path that contains at least one
+//   path separator (e.g. path/to/foo_test and
+//   /absolute/path/to/bar_test are fine, but foo_test is not).  This
+//   is rarely a problem as people usually don't put the test binary
+//   directory in PATH.
+//
+// TODO(wan@google.com): make thread-safe death tests search the PATH.
+
+// Asserts that a given statement causes the program to exit, with an
+// integer exit status that satisfies predicate, and emitting error output
+// that matches regex.
+# define ASSERT_EXIT(statement, predicate, regex) \
+    GTEST_DEATH_TEST_(statement, predicate, regex, GTEST_FATAL_FAILURE_)
+
+// Like ASSERT_EXIT, but continues on to successive tests in the
+// test case, if any:
+# define EXPECT_EXIT(statement, predicate, regex) \
+    GTEST_DEATH_TEST_(statement, predicate, regex, GTEST_NONFATAL_FAILURE_)
+
+// Asserts that a given statement causes the program to exit, either by
+// explicitly exiting with a nonzero exit code or being killed by a
+// signal, and emitting error output that matches regex.
+# define ASSERT_DEATH(statement, regex) \
+    ASSERT_EXIT(statement, ::testing::internal::ExitedUnsuccessfully, regex)
+
+// Like ASSERT_DEATH, but continues on to successive tests in the
+// test case, if any:
+# define EXPECT_DEATH(statement, regex) \
+    EXPECT_EXIT(statement, ::testing::internal::ExitedUnsuccessfully, regex)
+
+// Two predicate classes that can be used in {ASSERT,EXPECT}_EXIT*:
+
+// Tests that an exit code describes a normal exit with a given exit code.
+class GTEST_API_ ExitedWithCode {
+ public:
+  explicit ExitedWithCode(int exit_code);
+  bool operator()(int exit_status) const;
+ private:
+  // No implementation - assignment is unsupported.
+  void operator=(const ExitedWithCode& other);
+
+  const int exit_code_;
+};
+
+# if !GTEST_OS_WINDOWS
+// Tests that an exit code describes an exit due to termination by a
+// given signal.
+class GTEST_API_ KilledBySignal {
+ public:
+  explicit KilledBySignal(int signum);
+  bool operator()(int exit_status) const;
+ private:
+  const int signum_;
+};
+# endif  // !GTEST_OS_WINDOWS
+
+// EXPECT_DEBUG_DEATH asserts that the given statements die in debug mode.
+// The death testing framework causes this to have interesting semantics,
+// since the sideeffects of the call are only visible in opt mode, and not
+// in debug mode.
+//
+// In practice, this can be used to test functions that utilize the
+// LOG(DFATAL) macro using the following style:
+//
+// int DieInDebugOr12(int* sideeffect) {
+//   if (sideeffect) {
+//     *sideeffect = 12;
+//   }
+//   LOG(DFATAL) << "death";
+//   return 12;
+// }
+//
+// TEST(TestCase, TestDieOr12WorksInDgbAndOpt) {
+//   int sideeffect = 0;
+//   // Only asserts in dbg.
+//   EXPECT_DEBUG_DEATH(DieInDebugOr12(&sideeffect), "death");
+//
+// #ifdef NDEBUG
+//   // opt-mode has sideeffect visible.
+//   EXPECT_EQ(12, sideeffect);
+// #else
+//   // dbg-mode no visible sideeffect.
+//   EXPECT_EQ(0, sideeffect);
+// #endif
+// }
+//
+// This will assert that DieInDebugReturn12InOpt() crashes in debug
+// mode, usually due to a DCHECK or LOG(DFATAL), but returns the
+// appropriate fallback value (12 in this case) in opt mode. If you
+// need to test that a function has appropriate side-effects in opt
+// mode, include assertions against the side-effects.  A general
+// pattern for this is:
+//
+// EXPECT_DEBUG_DEATH({
+//   // Side-effects here will have an effect after this statement in
+//   // opt mode, but none in debug mode.
+//   EXPECT_EQ(12, DieInDebugOr12(&sideeffect));
+// }, "death");
+//
+# ifdef NDEBUG
+
+#  define EXPECT_DEBUG_DEATH(statement, regex) \
+  do { statement; } while (::testing::internal::AlwaysFalse())
+
+#  define ASSERT_DEBUG_DEATH(statement, regex) \
+  do { statement; } while (::testing::internal::AlwaysFalse())
+
+# else
+
+#  define EXPECT_DEBUG_DEATH(statement, regex) \
+  EXPECT_DEATH(statement, regex)
+
+#  define ASSERT_DEBUG_DEATH(statement, regex) \
+  ASSERT_DEATH(statement, regex)
+
+# endif  // NDEBUG for EXPECT_DEBUG_DEATH
+#endif  // GTEST_HAS_DEATH_TEST
+
+// EXPECT_DEATH_IF_SUPPORTED(statement, regex) and
+// ASSERT_DEATH_IF_SUPPORTED(statement, regex) expand to real death tests if
+// death tests are supported; otherwise they just issue a warning.  This is
+// useful when you are combining death test assertions with normal test
+// assertions in one test.
+#if GTEST_HAS_DEATH_TEST
+# define EXPECT_DEATH_IF_SUPPORTED(statement, regex) \
+    EXPECT_DEATH(statement, regex)
+# define ASSERT_DEATH_IF_SUPPORTED(statement, regex) \
+    ASSERT_DEATH(statement, regex)
+#else
+# define EXPECT_DEATH_IF_SUPPORTED(statement, regex) \
+    GTEST_UNSUPPORTED_DEATH_TEST_(statement, regex, )
+# define ASSERT_DEATH_IF_SUPPORTED(statement, regex) \
+    GTEST_UNSUPPORTED_DEATH_TEST_(statement, regex, return)
+#endif
+
+}  // namespace testing
+
+#endif  // GTEST_INCLUDE_GTEST_GTEST_DEATH_TEST_H_