>> 
>> still searching for some hints about "Carbonizer" Plug In...
>> 
>> Any idea where to look for ?
>
>this plugin works to determine what toolbox calls in the front most project
>may not be appropriate for os x.



The Carbonizer plug-in seems to be undocumented. 

It searches the source code of a project for toolbox calls, and compares them with a list of calls supported in Carbon. The list is similar to that in the Help file "OS-X Supported toolboxes", and it is not clear which version of CarbonLib it represents.

Some calls are wrongly stated to be unsupported, for example:
SetWTitle
DebugStr



There is an alternative method to test for missing toolbox calls.
Set the checkbox:
     Preferences/DBug/Insure validity of PPC toolboxes

This differs from the Carbonizer test in that it:

- is performed at program start-up on the compiled binary, not the source
- checks for zeros in the function-pointer table. These are toolbox routines that could not be linked to a library at run time.
- tests against the actual machine environment, not a file of supposedly supported toolbox calls
- takes only a few milliseconds
- checks the runtime as well as your code
- works for a PPC or Carbon compile
- works for a stand-alone single-file program
- has no *known* bugs  ;-)
- reports only failures, whereas Carbonizer also reports "Not recommended"

Personally, I find the advantages of the Preferences validity check sufficiently great that I have trashed Carbonizer. This may, however, be an egocentric view, because I wrote most of the validity-check code.

Robert P.