My cocoa app links to a number of C++ BSD Static libraries. These libraries are
built in Release configuration. They have Asset Macros in them.
The Asserts are fired in the release builds. My Windows programmer tele that
Asserts do not get compiled into release code on windows.
What are my op
On Jun 23, 2015, at 11:14 AM, Raglan T. Tiger wrote:
>
> Are these set in the Library project or the App project that links to them?
It'll have to be the library; the app project has no influence over what is
compiled into the library.
As a guess, you might want to define NDEBUG=1. That is *ve
Define the preprocessor symbol NDEBUG, and assert( ) calls will be ignored.
It’s simplest to add this in the Build Settings under “Preprocessor Macros”,
only for the Release configuration.
—Jens
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Apple's written policy is that crashy apps are not permitted in the
app store. Why is this not enforcd?
Pick a few apps at random. Sort the reviews by "Most Critical".
Quite common are complaints about crashing.
it is better not to ship a product at all than to ship a product that
drives away c
I'm running into an interesting exception being thrown by a watcher class that
pipes events around before they get to the expected class that will handle them.
In one special case where I rotate the device a "UIInternal" event is
intercepted by this class within an @try block an exception is thr
> On Jun 23, 2015, at 10:14 AM, Raglan T. Tiger wrote:
>
> My cocoa app links to a number of C++ BSD Static libraries. These libraries
> are built in Release configuration. They have Asset Macros in them.
>
> The Asserts are fired in the release builds. My Windows programmer tele that
> Ass
-rags
> On Jun 23, 2015, at 1:59 PM, Greg Parker wrote:
>
>
>> On Jun 23, 2015, at 10:14 AM, Raglan T. Tiger
>> wrote:
>>
>> My cocoa app links to a number of C++ BSD Static libraries. These libraries
>> are built in Release configuration. They have Asset Macros in them.
>>
>> The Asse
On Tue, Jun 23, 2015, at 02:54 PM, Alex Zavatone wrote:
> We don't care about motion events. We only care about touch events.
>
> I'm trying to check if the event is a of UIEventTypeMotion and simply
> return.
If you only care about touch events, why aren't you comparing against
UIEventTypeTouch
On Jun 23, 2015, at 5:35 PM, Raglan T. Tiger wrote:
>
> I have added NDEBUG=1 in the project release configurationpre-processor macro
> definitions per results here.
Just to be clear, =1 is actually not necessary. The standard is that if NDEBUG
is defined, assert is turned off. It's just my pe
> On Jun 23, 2015, at 5:48 PM, Scott Ribe wrote:
>
> Just to be clear, =1 is actually not necessary.
Yes. But of course Xcode puts DEBUG=1 in the debug configuration.
Just doing belt and suspenders.
What if the compiler did
#ifdef NDEBUG
if ( NDEBUG == 1 )
#endif
Just sayin'.
-rags
__
Actually, the rotate event is the one that is being caught and sent.
If it's a UIEvent and it's listed as a UIInternalEvent, within the debugger,
how do I check the type and subtype to see what type of event it is so that I
can return immediately if it is the wrong type?
On Jun 23, 2015, at 7:3
> On Jun 23, 2015, at 6:10 PM, Alex Zavatone wrote:
>
> Actually, the rotate event is the one that is being caught and sent.
>
> If it's a UIEvent and it's listed as a UIInternalEvent, within the debugger,
> how do I check the type and subtype to see what type of event it is so that I
> can re
On Jun 23, 2015, at 9:27 PM, Kyle Sluder wrote:
>> On Jun 23, 2015, at 6:10 PM, Alex Zavatone wrote:
>>
>> Actually, the rotate event is the one that is being caught and sent.
>>
>> If it's a UIEvent and it's listed as a UIInternalEvent, within the debugger,
>> how do I check the type and sub
From my limited job experience, most iOS apps are written by less than
competent programmers with a rushed deadline. There is no such concept of
quality control or even system design in general.
Take your example, this exposed a system design bug that the designer have draw
the line between har
> On Jun 23, 2015, at 7:31 PM, Alex Zavatone wrote:
>
>
> On Jun 23, 2015, at 9:27 PM, Kyle Sluder wrote:
>
>>> On Jun 23, 2015, at 6:10 PM, Alex Zavatone wrote:
>>>
>>> Actually, the rotate event is the one that is being caught and sent.
>>>
>>> If it's a UIEvent and it's listed as a UIInt
On Jun 23, 2015, at 10:50 PM, Kyle Sluder wrote:
>> On Jun 23, 2015, at 7:31 PM, Alex Zavatone wrote:
>
>>
>>
>> On Jun 23, 2015, at 9:27 PM, Kyle Sluder wrote:
>>
On Jun 23, 2015, at 6:10 PM, Alex Zavatone wrote:
Actually, the rotate event is the one that is being caught an
On Tue, Jun 23, 2015, at 10:20 PM, Alex Zavatone wrote:
> It's not being thrown by my own code. It's a rotate event that's being
> sent by the system.
[snip]
> The event's type doesn't match the enums. The event's type doesn't match
> any enum that I know of.
Again: your app needs to be OK wi
17 matches
Mail list logo
