crash in the carbon event loop

View: New views
17 Messages — Rating Filter:   Alert me  

crash in the carbon event loop

by Emmanuel Quetelard :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi

I have a weird crash in the carbon RunApplicationEventLoop() function.
According to the backtrace it crash somewhere in this method without touching one of my event handler.
To be more precise mouse events work just fine but keyboard events seem to crash the application.
Whatever I do with the handlers doesn't seem to change anything...(like disabling keyboard or mouse events handler or whatever..)

I don't have a clue of what I am doing wrong so if someone had this kind of problems all advices are welcome..

Emmanuel Quetelard.

_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Getting back into MacOSX development after some time off

by jerry porter :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,

I am returning back to Mac OSX development after some time off.

I am resurrecting an app I haven't touched since 2007.

I was able to get it to build to 10.5 SDK.

Any pointers in migrating to 10.6 SDK.

I know this is a rather general question.

Alse I am using MOKit.

Has anybody migrated MOKit to 10.6?

Thanks,
 Jerry Porter


     
_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Re: Getting back into MacOSX development after some time off

by Kiel Gillard :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


On 11/11/2009, at 2:36 PM, jerry porter wrote:

> Any pointers in migrating to 10.6 SDK.

Have you installed Mac OS X 10.6 on your development machine and tried changing the Base SDK of the project or the target to Mac OS X 10.6?

>
> I know this is a rather general question.

I also know this is a rather general answer. You'll have to be more specific.

The source for MOKit is available at <http://sourceforge.net/projects/mokit/files/>. You can modify that source to compile for 10.6 too.

Kiel

_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Re: Getting back into MacOSX development after some time off

by Steven Woolgar-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, 11 Nov 2009 14:51:49 +1100, Kiel Gillard wrote:

>
> On 11/11/2009, at 2:36 PM, jerry porter wrote:
>
>> Any pointers in migrating to 10.6 SDK.
>
> Have you installed Mac OS X 10.6 on your development machine and
> tried changing the Base SDK of the project or the target to Mac OS X
> 10.6?
>
>>
>> I know this is a rather general question.
>
> I also know this is a rather general answer. You'll have to be more
> specific.
>
> The source for MOKit is available at
> <http://sourceforge.net/projects/mokit/files/>. You can modify that
> source to compile for 10.6 too.

I took a look at it just now and it is pretty outdated.  There might be
some things of value, but I would consider just removing it from your
project and backfilling.



W.
_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Re: Getting back into MacOSX development after some time off

by jerry porter :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thanks,

I think I figured out how to "migrate" to 10.6 SDK in my code.
I started by playing with the Active SDK and the architecture settings.

I will just work my way through the deprecation warnings.

I have the source to MOKit and I will probably toss it once I have gotten up to speed on the new UI enhancements now available in 10.6.

I also have to get my head wrapped around the new IB too.
 Jerry Porter


- - -
When told the reason for daylight saving time the old Indian said ...


"Only a white man would believe that you could cut a foot off the top of a blanket and sew it to the bottom of a blanket and have a longer blanket."
- - -
- - -
Seen on a T-shirt: "Remember you are unique and special... Just like everyone else"
- - -



----- Original Message ----
From: Steven Woolgar <Steven_Woolgar@...>
To: macosx-dev@...
Sent: Tue, November 10, 2009 11:49:25 PM
Subject: Re: Getting back into MacOSX development after some time off

On Wed, 11 Nov 2009 14:51:49 +1100, Kiel Gillard wrote:

>
> On 11/11/2009, at 2:36 PM, jerry porter wrote:
>
>> Any pointers in migrating to 10.6 SDK.
>
> Have you installed Mac OS X 10.6 on your development machine and
> tried changing the Base SDK of the project or the target to Mac OS X
> 10.6?
>
>>
>> I know this is a rather general question.
>
> I also know this is a rather general answer. You'll have to be more
> specific.
>
> The source for MOKit is available at
> <http://sourceforge.net/projects/mokit/files/>. You can modify that
> source to compile for 10.6 too.

I took a look at it just now and it is pretty outdated.  There might be
some things of value, but I would consider just removing it from your
project and backfilling.



W.
_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev



     
_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Parent Message unknown re: crash in the carbon event loop

by geowar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, 11 Nov 2009 14:28:20 +1300, Emmanuel Quetelard <Emmanuel.Quetelard@...> wrote:
> I have a weird crash in the carbon RunApplicationEventLoop() function.
> According to the backtrace it crash somewhere in this method without touching one of my event handler.
> To be more precise mouse events work just fine but keyboard events seem to crash the application.
> Whatever I do with the handlers doesn't seem to change anything...(like disabling keyboard or mouse events handler or whatever..)

More often than not this is caused by you CFReleasing something that you shouldn't be releasing. The clang analyzer is good at picking up a lot of these unnecessary CFReleases. Use the "Build and Analyze" item in Xcode's "Build" menu.

Also, make sure you haven't turn off compiler and linker warnings. At the very least I'd max them out in my debug builds. You can cut-n-paste the following into your project (or target) build settings:

[BEGIN]

• All Configurations

ARCHS = $(ARCHS_STANDARD_32_BIT) x86_64
GCC_DYNAMIC_NO_PIC = NO
GCC_ENABLE_FIX_AND_CONTINUE = NO
GCC_PRECOMPILE_PREFIX_HEADER = YES
GCC_WARN_FOUR_CHARACTER_CONSTANTS = NO
PREBINDING = NO
ZERO_LINK = NO

• Debug

COPY_PHASE_STRIP = NO
DEBUG_INFORMATION_FORMAT = dwarf
GCC_FAST_OBJC_DISPATCH = NO
GCC_GENERATE_DEBUGGING_SYMBOLS = YES
GCC_OPTIMIZATION_LEVEL = 0
GCC_PREPROCESSOR_DEFINITIONS = $(value) DEBUG=1
GCC_WARN_ABOUT_MISSING_FIELD_INITIALIZERS = YES
GCC_WARN_ABOUT_MISSING_PROTOTYPES = YES
GCC_WARN_ABOUT_RETURN_TYPE = YES
GCC_WARN_CHECK_SWITCH_STATEMENTS = YES
GCC_WARN_EFFECTIVE_CPLUSPLUS_VIOLATIONS = NO
GCC_WARN_INITIALIZER_NOT_FULLY_BRACKETED = YES
GCC_WARN_MISSING_PARENTHESES = YES
GCC_WARN_PEDANTIC = NO
GCC_WARN_SHADOW = YES
GCC_WARN_TYPECHECK_CALLS_TO_PRINTF = YES
GCC_WARN_UNINITIALIZED_AUTOS = NO
GCC_WARN_UNKNOWN_PRAGMAS = YES
GCC_WARN_UNUSED_FUNCTION = YES
GCC_WARN_UNUSED_LABEL = YES
GCC_WARN_UNUSED_PARAMETER = YES
GCC_WARN_UNUSED_VALUE = YES
GCC_WARN_UNUSED_VARIABLE = YES
ONLY_ACTIVE_ARCH = YES
OTHER_CFLAGS = $(value) -Wimplicit-function-declaration
OTHER_CPLUSPLUSFLAGS =
WARNING_CFLAGS = -Wall -Wcast-align -Wchar-subscripts -Wextra -Wextra-tokens -Wformat=2 -Wpointer-arith -Wswitch-default -Wundef -Wwrite-strings

• Release

COPY_PHASE_STRIP = YES
DEBUG_INFORMATION_FORMAT = dwarf-with-dsym
GCC_FAST_OBJC_DISPATCH = YES
GCC_GENERATE_DEBUGGING_SYMBOLS = NO
GCC_OPTIMIZATION_LEVEL = s
ONLY_ACTIVE_ARCH = NO

• Current SDK & target OS

SDKROOT =
MACOSX_DEPLOYMENT_TARGET =

• Snow Leopard

MACOSX_DEPLOYMENT_TARGET = 10.6
SDKROOT = $(DEVELOPER_SDK_DIR)/MacOSX10.6.sdk

• PowerPC Leopard, Intel Snow Leopard and deploy to Tiger

SDKROOT = macosx10.6
SDKROOT[arch=ppc] = macosx10.5
MACOSX_DEPLOYMENT_TARGET = 10.4

[END]

With all the above warnings on build your debug configuration and pay attention to the warnings.

In the "Mac OS X Debugging Magic" technote (<http://developer.apple.com/mac/library/technotes/tn2004/tn2124.html>) read the section on tracing Carbon events:
<HIToolbox Event Debugging>. It may be of interest which event handler is being called when the crash occurs.

--
Enjoy,
George Warner,
Schizophrenic Optimization Scientist
Apple Developer Technical Support (DTS)

_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Parent Message unknown Re: Getting back into MacOSX development after some time off

by geowar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Tue, 10 Nov 2009 21:10:17 -0800 (PST), jerry porter <jep9816@...> wrote:
> I think I figured out how to "migrate" to 10.6 SDK in my code.
> I started by playing with the Active SDK and the architecture settings.

Remember that the SDK should be set to the NEWEST version of Mac OS X that you want to run on and the DEPLOYMENT_TARGET to the oldest. For example, for PowerPC Leopard, Intel Snow Leopard and deploy to Tiger:

SDKROOT = macosx10.6
SDKROOT[arch=ppc] = macosx10.5
MACOSX_DEPLOYMENT_TARGET = 10.4

You should probably be at least testing with an x86_64 architecture. I usually use:

ARCHS = $(ARCHS_STANDARD_32_BIT) x86_64

Note that this is the same for both debug and release configurations. If you only want to build the native architecture when debugging use this:

ONLY_ACTIVE_ARCH = YES

Note: the above build setting will cut-n-paste into your project or target build settings (if the appropriate table view has focus).
--
Enjoy,
George Warner,
Schizophrenic Optimization Scientist
Apple Developer Technical Support (DTS)

_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Re: Getting back into MacOSX development after some time off

by jerry porter :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thanks, that is a great help.
 Jerry Porter


- - -
When told the reason for daylight saving time the old Indian said ...


"Only a white man would believe that you could cut a foot off the top of a blanket and sew it to the bottom of a blanket and have a longer blanket."
- - -
- - -
Seen on a T-shirt: "Remember you are unique and special... Just like everyone else"
- - -




________________________________
From: Mr. George Warner <geowar@...>
To: macosx-dev@...
Cc: jerry porter <jep9816@...>
Sent: Wed, November 11, 2009 3:58:49 PM
Subject: Re: Getting back into MacOSX development after some time off


On Tue, 10 Nov 2009 21:10:17 -0800 (PST), jerry porter <jep9816@...> wrote:
> I think I figured out how to "migrate" to 10.6 SDK in my code.
> I started by playing with the Active SDK and the architecture settings.

Remember that the SDK should be set to the NEWEST version of Mac OS X that you want to run on and the DEPLOYMENT_TARGET to the oldest. For example, for PowerPC Leopard, Intel Snow Leopard and deploy to Tiger:


SDKROOT = macosx10.6
SDKROOT[arch=ppc] = macosx10.5
MACOSX_DEPLOYMENT_TARGET = 10.4

You should probably be at least testing with an x86_64 architecture. I usually use:

ARCHS = $(ARCHS_STANDARD_32_BIT) x86_64

Note that this is the same for both debug and release configurations. If you only want to build the native architecture when debugging use this:

ONLY_ACTIVE_ARCH = YES

Note: the above build setting will cut-n-paste into your project or target build settings (if the appropriate table view has focus).
--
Enjoy,
George Warner,
Schizophrenic Optimization Scientist
Apple Developer Technical Support (DTS)



     
_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Parent Message unknown re: crash in the carbon event loop

by Emmanuel Quetelard :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

> > More often than not this is caused by you CFReleasing something that you shouldn't be releasing. The clang analyzer is good at picking up a lot of these > > unnecessary CFReleases. Use the "Build and Analyze" item in Xcode's "Build" menu.

Actually when I don't release  any event, the crash still there, so it can't be that (or there is something I didn't understand) . Can it be a release of something else than an event that could cause this crash?

Thank you for the advises about the warning configuration, will be helpful..
_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Re: crash in the carbon event loop

by Kyle Sluder-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, Nov 11, 2009 at 5:57 PM, Emmanuel Quetelard
<Emmanuel.Quetelard@...> wrote:
> Actually when I don't release  any event, the crash still there, so it can't be that (or there is something I didn't understand) . Can it be a release of something else than an event that could cause this crash?

Any time you have a memory management bug, it can manifest itself as
something else.  And since you didn't post your code or the backtrace,
there's really nothing more informative anyone can say.

Things to take away:

1) If you crash, it's usually because of an over-release.
2) You should be running the clang static analyzer frequently.
Especially after you crash.
3) If fixing the static analyzer's warnings doesn't help, and you
decide to post to a mailing list, you need to include the backtrace
and any code involved.

--Kyle Sluder
_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Parent Message unknown re: crash in the carbon event loop

by geowar :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Thu, 12 Nov 2009 14:57:57 +1300, Emmanuel Quetelard <Emmanuel.Quetelard@...> wrote:
>>  More often than not this is caused by you CFReleasing something that you shouldn't be releasing.

> Actually when I don't release  any event, the crash still there, so it can't be that (or there is something I didn't understand) .


The only events you should ever release are ones that you create, copy or retain; all events passed to your handlers are released by the OS after your handler returns.

> Can it be a release of something else than an event that could cause this crash?


Yes; Specifically Core Foundation (CF) objects. Look for CFRelease's and make sure the object they're releasing were created, copied or retained by you. If they were passed to you or came from a "get" function then you should only release them if you retained them at some point.

--
Enjoy,
George Warner,
Schizophrenic Optimization Scientist
Apple Developer Technical Support (DTS)

_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Parent Message unknown re: crash in the carbon event loop

by Emmanuel Quetelard :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Here is the backtrace of my crash:

#0 0x005f1c28 in GC_free at malloc.c:411
#1 0x91b0e768 in HIObject::HandleClassHIObjectEvent
#2 0x91b0e5d3 in HIObject::EventHook
#3 0x91b0e13d in DispatchEventToHandlers
#4 0x91b0d57b in SendEventToEventTargetInternal
#5 0x91b0d3e0 in SendEventToEventTargetWithOptions
#6 0x91b4ce22 in HIObject::Destruct
#7 0x91251516 in _CFRelease
#8 0x91c5f7e2 in MenuData::~MenuData
#9 0x91b0e768 in HIObject::HandleClassHIObjectEvent
#10 0x91b0e5d3 in HIObject::EventHook
#11 0x91b0e13d in DispatchEventToHandlers
#12 0x91b0d57b in SendEventToEventTargetInternal
#13 0x91b0d3e0 in SendEventToEventTargetWithOptions
#14 0x91b4ce22 in HIObject::Destruct
#15 0x91251516 in _CFRelease
#16 0x91b8cdfa in ReleaseMenu
#17 0x91b8bf5e in SystemAppMenuHandler
#18 0x91b0e13d in DispatchEventToHandlers
#19 0x91b0d57b in SendEventToEventTargetInternal
#20 0x91b0d3e0 in SendEventToEventTargetWithOptions
#21 0x91b51fb9 in SendMenuPopulate
#22 0x91b51e73 in PopulateMenu
#23 0x91b514dc in Check1MenuForKeyEvent
#24 0x91b50cda in CheckMenusForKeyEvent
#25 0x91b50939 in _IsMenuKeyEvent
#26 0x91b50685 in IsMenuKeyEvent
#27 0x91c08a52 in HIMenuBar::HandleKeyboardEvent
#28 0x91b0e649 in HIObject::EventHook
#29 0x91b0e13d in DispatchEventToHandlers
#30 0x91b0d57b in SendEventToEventTargetInternal
#31 0x91b0d3e0 in SendEventToEventTargetWithOptions
#32 0x91b3c307 in ToolboxEventDispatcherHandler
#33 0x91b0e4f6 in DispatchEventToHandlers
#34 0x91b0d57b in SendEventToEventTargetInternal
#35 0x91b29ecc in SendEventToEventTarget

last call of my code from here
#36 0x00178c5a in AGLWindowManager::processEvents at macosx_agl.mm:1089
#37 0x0017610b in WindowManager::mainLoop at wm_common.cpp:33
#38 0x0004e85d in main_layer_load at emitter.cpp:5378
#39 0x00006b6c in main at main.cpp:313

here is the code of the function processing events :

int AGLWindowManager::processEvents(void)
{
   //RunApplicationEventLoop();
       
       
   EventRef event;
   EventRecord oldStyleMacEvent;
   EventTargetRef eventDispatcher = GetEventDispatcherTarget();

   while (ReceiveNextEvent(0, NULL, 0.0, TRUE, &event)==noErr) {
      if (ConvertEventRefToEventRecord(event, &oldStyleMacEvent)) {
         if (oldStyleMacEvent.what==kHighLevelEvent) {
            AEProcessAppleEvent(&oldStyleMacEvent);
         }
      }
         
      SendEventToEventTarget(event, eventDispatcher);
      //ReleaseEvent(event);
   }

   return(0);
}

_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Parent Message unknown Re: Getting back into MacOSX development after some time off

by Matt Neuburg :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, 11 Nov 2009 12:58:49 -0800, "Mr. George Warner" <geowar@...>
said:
>On Tue, 10 Nov 2009 21:10:17 -0800 (PST), jerry porter <jep9816@...>
wrote:
>> I think I figured out how to "migrate" to 10.6 SDK in my code.
>> I started by playing with the Active SDK and the architecture settings.
>
>Remember that the SDK should be set to the NEWEST version of Mac OS X that you
want to run on and the DEPLOYMENT_TARGET to the oldest. For example, for PowerPC
Leopard, Intel Snow Leopard and deploy to Tiger:
>
>SDKROOT = macosx10.6
>SDKROOT[arch=ppc] = macosx10.5
>MACOSX_DEPLOYMENT_TARGET = 10.4

I often hear this stated as the "conventional wisdom", but my own experience
is that if I do that, I don't get the warnings I need in order to discover
that my app is not backwards compatible. m.

--
matt neuburg, phd = matt@..., <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
http://www.tidbits.com/matt/default.html#applescriptthings



_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Re: Getting back into MacOSX development after some time off

by jerry porter :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thank,

However I am not to concerned with being backward compatible.

I just want to move my code forward.

BTW so far so good, purging out the warnings so far.

 Jerry Porter


- - -
When told the reason for daylight saving time the old Indian said ...


"Only a white man would believe that you could cut a foot off the top of a blanket and sew it to the bottom of a blanket and have a longer blanket."
- - -
- - -
Seen on a T-shirt: "Remember you are unique and special... Just like everyone else"
- - -



----- Original Message ----
From: Matt Neuburg <matt@...>
To: macosx-dev@...
Sent: Mon, November 16, 2009 1:09:27 PM
Subject: Re: Getting back into MacOSX development after some time off

On Wed, 11 Nov 2009 12:58:49 -0800, "Mr. George Warner" <geowar@...>
said:
>On Tue, 10 Nov 2009 21:10:17 -0800 (PST), jerry porter <jep9816@...>
wrote:
>> I think I figured out how to "migrate" to 10.6 SDK in my code.
>> I started by playing with the Active SDK and the architecture settings.
>
>Remember that the SDK should be set to the NEWEST version of Mac OS X that you
want to run on and the DEPLOYMENT_TARGET to the oldest. For example, for PowerPC
Leopard, Intel Snow Leopard and deploy to Tiger:
>
>SDKROOT = macosx10.6
>SDKROOT[arch=ppc] = macosx10.5
>MACOSX_DEPLOYMENT_TARGET = 10.4

I often hear this stated as the "conventional wisdom", but my own experience
is that if I do that, I don't get the warnings I need in order to discover
that my app is not backwards compatible. m.

--
matt neuburg, phd = matt@..., <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
http://www.tidbits.com/matt/default.html#applescriptthings



_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev



     
_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Re: Getting back into MacOSX development after some time off

by Izidor Jerebic :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


On 16.11.2009, at 19:09, Matt Neuburg wrote:

>> SDKROOT = macosx10.6
>> SDKROOT[arch=ppc] = macosx10.5
>> MACOSX_DEPLOYMENT_TARGET = 10.4
>
> I often hear this stated as the "conventional wisdom", but my own  
> experience
> is that if I do that, I don't get the warnings I need in order to  
> discover
> that my app is not backwards compatible. m.

Interesting. What are those "warnings I need" you don't get?

The only problems I had were with new/obsolete delegate methods,  
because compiler doesn't know which are going to be called and which  
are not going to be called. And no SDK setting can help you with that.


izidor

_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Re: Getting back into MacOSX development after some time off

by Uli Kusterer-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 17.11.2009, at 10:00, Izidor Jerebic wrote:
> Interesting. What are those "warnings I need" you don't get?


I'm not Matt, but the issue he's probably referring to is calling methods that are only available in the newer OS versions. The compiler/linker will not tell you that you're calling one of those, and that you need to add checks or fallbacks for the older OS versions you support.

OTOH, by using the oldest system version you support as the SDK, you *can't* call any newer APIs by accident, as they're simply not defined. If you really want to use newer API, you have to jump through a few hoops, of course (put new-OS-specific code in a loadable bundle, declare the methods yourself and look them up manually, or whatever else is appropriate in your case). The difference is, you're making the compatibility-breaking calls explicit.

Cheers,
-- Uli Kusterer
"The witnesses of TeachText are everywhere..."



_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev

Parent Message unknown Re: Getting back into MacOSX development after some time off

by Matt Neuburg :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Fri, 20 Nov 2009 12:04:45 +0100, Uli Kusterer <kusterer@...> said:
>On 17.11.2009, at 10:00, Izidor Jerebic wrote:
>> Interesting. What are those "warnings I need" you don't get?
>
>I'm not Matt, but the issue he's probably referring to is calling methods that
are only available in the newer OS versions. The compiler/linker will not tell
you that you're calling one of those

Yes, that's exactly what I was referring to. m.

--
matt neuburg, phd = matt@..., <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
http://www.tidbits.com/matt/default.html#applescriptthings



_______________________________________________
MacOSX-dev mailing list
MacOSX-dev@...
http://www.omnigroup.com/mailman/listinfo/macosx-dev