Mac Forum / Programming / CodeWarrior / December 2003

Hmm, I guess the subject says it all.
For those who have localized PowerPlant apps (esp. on OS X), what
strategy do you use?  Specifically, I'm wondering how best to localize
various PPobs for Windows and Views.   Constructor apparently does not

I get the following error when building a shared library.
Error : Reference from dylib libicudata.dylib.28(version 00000000) to
symbol '___kill_critical_regions' from dylib
          libicudata.dylib.28(version 00000000) not resolved

Any suggestions on the state of profiling MacOSX programs for
CodeWarrior users?
Last I remember, the CodeWarrior profiler libraries (or CityView's
AppBeat) were pretty useless in lengthy preemptive multithreaded

I have been told that, when targeting OS X exclusively (as PPx does),
malloc() is threadsafe.
I would like to use veclib (BLAS) inside MP threads (targeting OS 10.2+).
Is there anything, in CW or in general, that would cause unsafe MP

I ran into a very frustrating debugging issue with Pro 8.3 last night.
In short, I've got a CFM app that uses a lot of CFString and CFXML
stuff. As fate would have it, I was using some Apple sample CFXML code
to tinker with XML. The sample code in question is here:

I remember there is a #somthing to display messages when we compile but i
totally forgot what it is.
#message ?
#warning displays a warning sign, i can't remember which one it is for

I purchased and installed v.9 a few months ago, installed the license.dat
file, and it worked fine until I upgraded to Panther 10.3.1.
Now, I get error messages like this when compiling C++:
Error   : Unable to use the plugin "Metrowerks C/C++". It is licensed and a

What is the best way to manage threading in C++ on the Mac?
Pro 9 on the Mac has introduced a new library:  Metrowerks::threads,
found in <msl_thread>.  This is a thin C++ wrapper over the native OS
threading interface.  On Mach-O, Metrowerks::threads relies on

I am porting a client-server project from Mac Classic to OS X.
On System 9 the client had filetype 'APPL' and launched automatically
the  BOA server of filetype 'appe'. This worked fine over years with
LaunchApplication().

FWIW, I am not able to use MallocDebug on any of my Carbon CFM apps
(compiling with CW 9.1, but this holds true for CW 9 and CW 8.3 as
well). They crash immediately, and the Console crash.log reports the
following:

My Carbon application is building fine, but I notice it is showing the
default application icon instead of the one from my app resources.
Upon investigation, I discover this is because CW 8 is not setting the
"Has BNDL" finder flag in the completed application. How do I tell CW 8

I can't be the only one who has this bug:
I'm using CW 9.1, but since CW 9 I've had a problem where certain
functions I've defined will not appear in the function popup list in
the source window after I've added the file to my current project.

I have this code:
 #include <iostream>
 #include <bitset>
 template< std::size_t N >

I have created a project using Mac OS PowerPlant Stationary -> Mac OS
Carbon -> Basic. When i run the project, the executable generated by
the project has the name "Basic PowerPlant Carbon" by default. The
problem is when i run the application (executable generated by my

CW 9
Reference CD : Thrill Seekers : Cheap Thrill : Cheap Thrill.jpg
?