Re: Xerces CodeWarrior Projects

[James Berry <jb...@criticalpath.com>]

Hi Urs,

Thanks for your comments. (I address them a bit below). I don't believe any
of this should hold up a 2.0 release, as these are long-standing issues.

On 7/22/02 9:44 AM, "Urs Muff" <um...@quark.com> wrote:

> Do you guys know that CodeWarrior is supporting __declspec(export),
> __declspec(import)?
> If you are interested, I have a CodeWarrior 8.1 project to create a Mach-O
> Framework [using the Metroworks linker instead of the Apple one].

This is worth looking into. If you want to supply me with the project, I'd
be happy to look at it as a future extension. I believe it's basically just
a matter of setting the macros (PLATFORM_EXPORT/PLATFORM_IMPORT) in the
CodeWarriorDefs.hpp file, right?

> Any function declared to be exported should also have a specific calling
> convention [using __stdcall, __cdecl, or __pascal].  This allows to have a
> different standard setting when using the Xerces library.

This would be more cumbersome as it requires a change to each function,
correct? Is this for Windows use? On PPC the calling conventions are all the
same, right?

> Also you should not mix system includes and user includes.  [CodeWarrior is
> very confused about that].  I know that in any other platform a #include
> "xxx" will look in the current folder, but CodeWarrior is not.  Any public
> header should either use #include <>, or #include "", exclusively.  Right
> know those includes are mixed and causing headaches with CodeWarrior access
> path settings.

Yeah, this is a long-standing issue with the Xerces source. I haven't found
it too difficult to make this work correctly in the CodeWarrior projects by
simply supplying the access path twice: once in user paths and once in
system paths. But I agree it's non-optimal. Would you be interested in
supplying a patch?

> Please let me know if I should log bugs for those issues?

Sure, feel free to. One could reference the external declaration macros for
CodeWarrior, the other could be more generic to the entire Xerces source,
and reference the <>/"" issue.

James.
> 
> - URS C. MUFF
> SYSTEMS ARCHITECT       - RESEARCH LAB
> UMUFF@QUARK.COM      - X6360
> +1 (303) 894 3360
> 
> -----Original Message-----
> From: James Berry [mailto:jberry@criticalpath.com]
> Sent: Monday, July 22, 2002 10:37 AM
> To: Xerces C Dev
> Subject: Re: Plan for Xerces-C++ 2.0.0
> 
> Hi Tinny,
> 
> Whoops. I was on vacation last week.
> 
> I just slipped in a change to the unix makefiles, and changes to the Mac OS
> project files to account for new newly added files. I think this should slip
> the 2.0 release by a day.
> 
> James.
> 
> On 7/22/02 7:40 AM, "tng-xml@ca.ibm.com" <tn...@ca.ibm.com> wrote:
> 
>> The candidate Xerces-C++ 2.0 packages are now available in
>> http://xml.apache.org/dist/xerces-c/nightly/2002-07-22/.   Please check
> and
>> let me know any problem.  If nothing severe is reported, the same packages
>> will be released officialy within the next day.  Thanks!
>> 
>> Tinny
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
>> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>> 
>> 
> 
> --
> /**********************************
> James D. Berry
> mailto:jberry@criticalpath.com
> vox:503.265.1213 fax:503.222.3020
> **********************************/
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
> 
> 

--
/**********************************
 James D. Berry
 mailto:jberry@criticalpath.com
 vox:503.265.1213 fax:503.222.3020
 **********************************/



---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org