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.

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

when the interface be mocked is big, to compile the mock object become slowly #33

Closed
GoogleCodeExporter opened this issue Jun 25, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

  now google mock framework implement the mock object in the corresponding
class. And when I used the mock object, I have to include the mock class in
my source code, if the interface that I mocked is big, when I compile my
source code, it is very very slowy. 
  I hope that when google mock implement the mock object, it can sperate
the declare file and implement file, that means I can comiple the mock
object to a single .obj file. I think this way can compile my source code
fastly.


Original issue reported on code.google.com by zouy...@gmail.com on 17 Feb 2009 at 11:04

@GoogleCodeExporter
Copy link
Author

This is determined by GoogleMock's fundamental design and cannot be changed.  
Having
the implementation in the .h file makes it convenient to use the mock class.

How big is your interface?  What compiler are you using?  How slow was it?  Do 
you
really need to mock everything in the interface?

Original comment by zhanyong...@gmail.com on 19 Feb 2009 at 8:23

  • Changed state: WontFix
  • Added labels: OpSys-All, Priority-Low, Type-Enhancement
  • Removed labels: Priority-Medium, Type-Defect

@GoogleCodeExporter
Copy link
Author

Original comment by w...@google.com on 18 Oct 2010 at 6:50

  • Changed state: Duplicate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant