C++根据.h文件批量生成需要的函数框架
类似VS中添加类 A的方法 int abc();
会在对应的实现文件.cpp中自动生成,
int A::abc() {
}
初学python,尝试写了一个脚本,自动根据写好的.h文件完成这一工作,也支持模板类,不过没考虑太多模板可能会有bug。
也可能会有很多其他的bug,不过用了下,感觉还可以,有错误再改正:)
用法
比如有一个abc.h,对应的实现文件abc.cc
1.新建一个abc.cc文件
touch abc.cc
2.运行脚本
./prodef.py abc.h abc.cc
因为我默认是.cc文件,也可
./prodef.py abc.h
用google 开源的代码做了一个实验,
我们要处理的gtest-test-part.h如下
// Copyright 2008, Google Inc.
// All rights reserved.
#ifndef GTEST_INCLUDE_GTEST_GTEST_TEST_PART_H_
#define GTEST_INCLUDE_GTEST_GTEST_TEST_PART_H_
#include <iosfwd>
#include <gtest/internal/gtest-internal.h>
#include <gtest/internal/gtest-string.h>
namespace testing {
// The possible outcomes of a test part (i.e. an assertion or an
// explicit SUCCEED(), FAIL(), or ADD_FAILURE()).
enum TestPartResultType {
TPRT_SUCCESS, // Succeeded.
TPRT_NONFATAL_FAILURE, // Failed but the test can continue.
TPRT_FATAL_FAILURE // Failed and the test should be terminated.
};
// A copyable object representing the result of a test part (i.e. an
// assertion or an explicit FAIL(), ADD_FAILURE(), or SUCCESS()).
//
// Don't inherit from TestPartResult as its destructor is not virtual.
class TestPartResult {
public:
// C'tor. TestPartResult does NOT have a default constructor.
// Always use this constructor (with parameters) to create a
// TestPartResult object.
TestPartResult(TestPartResultType type,
const char* file_name,
int line_number,
const char* message)
: type_(type),
file_name_(file_name),
line_number_(line_number),
summary_(ExtractSummary(message)),
message_(message) {
}
// Gets the outcome of the test part.
TestPartResultType type() const { return type_; }
// Gets the name of the source file where the test part took place, or
// NULL if it's unknown.
const char* file_name() const { return file_name_.c_str(); }
// Gets the line in the source file where the test part took place,
// or -1 if it's unknown.
int line_number() const { return line_number_; }
// Gets the summary of the failure message.
const char* summary() const { return summary_.c_str(); }
// Gets the message associated with the test part.
const char* message() const { return message_.c_str(); }
// Returns true iff the test part passed.
bool passed() const { return type_ == TPRT_SUCCESS; }
// Returns true iff the test part failed.
bool failed() const { return type_ != TPRT_SUCCESS; }
// Returns true iff the test part non-fatally failed.
bool nonfatally_failed() const { return type_ == TPRT_NONFATAL_FAILURE; }
// Returns true iff the test part fatally failed.
bool fatally_failed() const { return type_ == TPRT_FATAL_FAILURE; }
private:
TestPartResultType type_;
// Gets the summary of the failure message by omitting the stack
// trace in it.
static internal::String ExtractSummary(const char* message);
// The name of the source file where the test part took place, or
// NULL if the source file is unknown.
internal::String file_name_;
// The line in the source file where the test part took place, or -1
// if the line number is unknown.
int line_number_;
internal::String summary_; // The test failure summary.
internal::String message_; // The test failure message.
};
// Prints a TestPartResult object.
std::ostream& operator<<(std::ostream& os, const TestPartResult& result);
// An array of TestPartResult objects.
//
// We define this class as we cannot use STL containers when compiling
// Google Test with MSVC 7.1 and exceptions disabled.
//
// Don't inherit from TestPartResultArray as its destructor is not
// virtual.
class TestPartResultArray {
public:
TestPartResultArray();
~TestPartResultArray();
// Appends the given TestPartResult to the array.
void Append(const TestPartResult& result);
// Returns the TestPartResult at the given index (0-based).
const TestPartResult& GetTestPartResult(int index) const;
// Returns the number of TestPartResult objects in the array.
int size() const;
private:
// Internally we use a list to simulate the array. Yes, this means
// that random access is O(N) in time, but it's OK for its purpose.
internal::List<TestPartResult>* const list_;
GTEST_DISALLOW_COPY_AND_ASSIGN_(TestPartResultArray);
};
// This interface knows how to report a test part result.
class TestPartResultReporterInterface {
public:
virtual ~TestPartResultReporterInterface() {}
virtual void ReportTestPartResult(const TestPartResult& result) = 0;
};
namespace internal {
// This helper class is used by {ASSERT|EXPECT}_NO_FATAL_FAILURE to check if a
// statement generates new fatal failures. To do so it registers itself as the
// current test part result reporter. Besides checking if fatal failures were
// reported, it only delegates the reporting to the former result reporter.
// The original result reporter is restored in the destructor.
// INTERNAL IMPLEMENTATION - DO NOT USE IN A USER PROGRAM.
class HasNewFatalFailureHelper : public TestPartResultReporterInterface {
public:
HasNewFatalFailureHelper();
virtual ~HasNewFatalFailureHelper();
virtual void ReportTestPartResult(const TestPartResult& result);
bool has_new_fatal_failure() const { return has_new_fatal_failure_; }
private:
bool has_new_fatal_failure_;
TestPartResultReporterInterface* original_reporter_;
GTEST_DISALLOW_COPY_AND_ASSIGN_(HasNewFatalFailureHelper);
};
} // namespace internal
} // namespace testing
#endif // GTEST_INCLUDE_GTEST_GTEST_TEST_PART_H_
运行 ./prodef.py gtest-test-part.h
生成的 gtest-test-part.cc 函数框架如下
#include "gtest-test-part.h"
namespace testing {
// Gets the summary of the failure message by omitting the stack
// trace in it.
internal::String TestPartResult::ExtractSummary(const char* message) {
}
// Prints a TestPartResult object.
std::ostream& operator<<(std::ostream& os, const TestPartResult& result) {
}
TestPartResultArray::TestPartResultArray() {
}
TestPartResultArray::~TestPartResultArray() {
}
// Appends the given TestPartResult to the array.
void TestPartResultArray::Append(const TestPartResult& result) {
}
// Returns the TestPartResult at the given index (0-based).
const TestPartResult& TestPartResultArray::GetTestPartResult(int index) const {
}
// Returns the number of TestPartResult objects in the array.
int TestPartResultArray::size() const {
}
void TestPartResultReporterInterface::ReportTestPartResult(const TestPartResult& result) {
}
namespace internal {
HasNewFatalFailureHelper::HasNewFatalFailureHelper() {
}
HasNewFatalFailureHelper::~HasNewFatalFailureHelper() {
}
void HasNewFatalFailureHelper::ReportTestPartResult(const TestPartResult& result) {
}
} // namespace internal
} // namespace testing
下面是程序源码
#!/usr/local/bin/python3.0
#autor goldenlock@pku
#05.13.09
C++根据.h文件批量生成需要的函数框架相关推荐
- 如何通过TXT文件批量生成EAN14条码
EAN14条形码是基于EAN-128码的编码规则,长度是14位,第14位为校验位,由前面13位计算得出.EAN14条形码通常会用来制作集装箱编号条码.批量制作条码时,我们一般会通过导入数据库的方式来实 ...
- 使用Excel文件批量生成Codabar码
Codabar(库德巴码)是由Monarch Marking Systems在1972年研制的条形码.它是在"2 of 5"后早期阶段引入的条形码.广泛用于需要序列号的领域,如血库 ...
- 通过Excel文件批量生成Code 39扩展码
code39码是条形码的一种,编码简单.能够对任意长度的数据进行编码.支持设备广泛,所以code39码是最常用的条形码之一.code39码在条码打印软件中有两种表现类型:标准code39码和支持字符更 ...
- 通过TXT文件批量生成UPC-A条码
UPC码算是EAN条码的前身,因此两者有着类似的特性及编码方式.UPC码分为标准型UPC-A码及简易型UPC-E码,UPC-A条码左侧6个条码字符均由A子集的条码字符组成,右侧数据符及校验符均由C子集 ...
- TXT文件批量生成二维码
大多数人在制作标签时,数据库文件都选择Excel文件,其实TXT文件在作为数据库时,也是可以制作各种可变数据标签的,比如批量生成二维码,条形码等.下面我们就使用TXT文件作为数据库批量生成二维码. 打 ...
- unity导出fbx模型_Unity批量合并Animation工具/根据已有的Animation文件批量生成带FBX动画工具...
由于本人现有项目的项目素材大部分都需要继续沿用旧项目的模型与动画,但在接受旧模型动画的时候发现,模型动画由于外包已经丢失了3dmax的源文件,只剩下了一堆AnimationCilp(.anim)文件与 ...
- 用Python写一个批量生成账号的函数(用户控制数据长度、数据条数)
# 1.写一个函数,批量生成一些注册使用的账号:产生的账号是以@163.com结尾,长度由用户输入,产生多少条也由用户输入,用户名不能重复,用户名必须由大写字母.小写字母.数字组成 import ra ...
- CodeSmith将模板文件批量生成文件的方法
以前写codeSmith模板的时候,如果直接像asp一样混排编写的话,代码输出来codeSmith中,不知道怎么保存到文件,后来把所有要输出的模板文字都用stringBuiler串接起来然后IO到文件 ...
- Python读取Execl文件批量生成二维码
#参考他人稍微修改 引入包 import qrcode import xlrd 代码 生成二维码 def create_qrcode(file_name, content): img = qrcode ...
最新文章
- python软件怎么用-用Python如何打出你的第一个程序
- 京东每日特价专栏仿写
- 综合布线中所需要的的带宽和数据速率
- hibernate之CRUD操作
- VC打包程序,并修改注册表(详细以后补充)
- 4008-基于邻接矩阵的新边的增加(C++,附思路)
- c++和java哪个难_为什么说C语言比Java难?
- lc滤波电路电感电容值选择_模拟电路中,电感的这些知识点你都清楚吗?
- linux下client命令,Linux系统smbclient命令的使用方法
- 一篇比较好的高数的学习规划分享
- 必须掌握,二叉树的前中后序遍历(迭代+递归)详细代码
- 硬币组合问题-非递归实现
- 自动驾驶最全基础知识、课程、论文、数据集、开源软件等资源整理分享
- Swift5实现ios后台播放语音,腾讯音视频通话后台播放来电铃声
- javaFX 学习之 超链接(HyperLink) 转载
- 从技术实现到安全运行,工程师版“元宇宙”离我们还有多远?
- DAO 中独特的通证经济
- OpenGL ES 实现瘦脸大眼效果
- 试用 网络存储器(ReadyNAS NV+)
- 网站下拉菜单,选择下拉后自动填充(图)