why can I not just pass an int or bool directly into the OCMock's "andReturnValue" argument?

Question

I was trying to do:

[[[mockQuestion stub] andReturnValue:YES] shouldNegate];
[[[mockQuestion stub] andReturnValue:123] randomNumberWithLimit];

But that gave me this warning/error "incompatible integer pointer conversion sending 'BOOL' (aka 'signed char') to parameter of type 'NSValue *'"

The only way I could figure out to get around it was to do:

BOOL boolValue = YES;
int num = 123;

[[[mockQuestion stub] andReturnValue:OCMOCK_VALUE(boolValue)] shouldNegate];
[[[mockQuestion stub] andReturnValue:OCMOCK_VALUE(num)] randomNumberWithLimit];

But that makes my test code seem so overly verbose.. Is there a way to do this all inline without having to set variables?

score 3 · Accepted Answer · answered Aug 16 '12 at 23:11

3

You can use a literal style that looks like (type){value}. This is commonly used to create struct literals but works for basic datatypes too. The important aspect here is that this type of literal creates a temporary that can be addressed. This means you can write your code like

[[[mockQuestion stub] andReturnValue:OCMOCK_VALUE((BOOL){YES})] shouldNegate];
[[[mockQuestion stub] andReturnValue:OCMOCK_VALUE((int){123})] randomNumberWithLimit];

answered Aug 16 '12 at 23:11

Lily Ballard

182,031
33
381
347

Thanks, this should remove a fair amount of boilerplate in my tests! – Christopher Pickslay Aug 20 '12 at 19:54
Didn't know about this syntax either. Is it new? I'll update the OCMock documentation accordingly. – Erik Doernenburg Aug 23 '12 at 15:31
@ErikDoernenburg: They're called "Compound Literals" and they were introduced in C99. So they've been around for over a decade, although for some reason they haven't been very well-known. – Lily Ballard Aug 23 '12 at 19:17

score 0 · Answer 2 · answered Aug 16 '12 at 23:12

0

The parameter is supposed to be an object pointer. In this case it should point to an object of the NSValue class.

answered Aug 16 '12 at 23:12

Jim

5,940
9
44
91

why can I not just pass an int or bool directly into the OCMock's "andReturnValue" argument?

2 Answers2