FROM : Chris Hanson
DATE : Wed Aug 30 09:18:53 2006
On Aug 28, 2006, at 8:44 PM, Dominic Cooney wrote:
> I'm a Mac OS X neophyte taking refuge from Windows. I'm having a
> little trouble building Omni's source code product. Has anyone
> encountered this particular issue--linker unsatisfied for
> should/shouldBeEqual/etc. already?
It's important to mention what development environment and operating
system version you're using.
I suspect you're using Xcode 2.3 or 2.4, where certain of the
original OCUnit macros were deprecated, and Omni's project is built
for Xcode 2.2 or an earlier version where those macros were still
available. If you look at <SenTestingKit/SenTestCase_Macros.h> you
can see the preprocessor symbol you need to define in order to enable
these deprecated macros for your target or project.
The reason these macros were deprecated is that any macros pollute
the global namespace, and the STAssert... prefixed macros don't have
nearly the potential for conflict with regular identifiers that
macros like "should" and "fail" do. In fact, "fail" conflicts with
an identifier in Standard C++ which can be an issue if you try to
write unit tests for Objective-C++ code.
-- Chris
DATE : Wed Aug 30 09:18:53 2006
On Aug 28, 2006, at 8:44 PM, Dominic Cooney wrote:
> I'm a Mac OS X neophyte taking refuge from Windows. I'm having a
> little trouble building Omni's source code product. Has anyone
> encountered this particular issue--linker unsatisfied for
> should/shouldBeEqual/etc. already?
It's important to mention what development environment and operating
system version you're using.
I suspect you're using Xcode 2.3 or 2.4, where certain of the
original OCUnit macros were deprecated, and Omni's project is built
for Xcode 2.2 or an earlier version where those macros were still
available. If you look at <SenTestingKit/SenTestCase_Macros.h> you
can see the preprocessor symbol you need to define in order to enable
these deprecated macros for your target or project.
The reason these macros were deprecated is that any macros pollute
the global namespace, and the STAssert... prefixed macros don't have
nearly the potential for conflict with regular identifiers that
macros like "should" and "fail" do. In fact, "fail" conflicts with
an identifier in Standard C++ which can be an issue if you try to
write unit tests for Objective-C++ code.
-- Chris
| Related mails | Author | Date |
|---|---|---|
| Dominic Cooney | Aug 29, 05:44 | |
| Chris Hanson | Aug 30, 09:18 |






Cocoa mail archive

