Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Need to unify the way the GTEST_* macros are interpreted #49

Closed
GoogleCodeExporter opened this issue May 27, 2015 · 1 comment
Closed

Need to unify the way the GTEST_* macros are interpreted #49

GoogleCodeExporter opened this issue May 27, 2015 · 1 comment
Labels
auto-migrated OpSys-All Priority-Medium Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

Some GTEST_* macros have two states: defined vs undefined, e.g. 
GTEST_OS_MAC.  Some GTEST_* macros have either 0 or 1 values, e.g. 
GTEST_IS_THREADSAFE.  Try to use the same convention across the board.

Original issue reported on code.google.com by shiq...@gmail.com on 11 Oct 2008 at 6:52
@GoogleCodeExporter
Copy link
Author 

I have a fix that will go in on Monday.

Original comment by zhanyong...@gmail.com on 22 Feb 2009 at 5:48

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated OpSys-All Priority-Medium Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter