[ace-users] ACE_TCHAR use in ACE_OS

Bennett, Patrick Patrick.Bennett at inin.com
Wed Jul 18 13:18:08 CDT 2007

No, do NOT switch it to only have one version!!!
A special 'unicode' build should not be (and is not) required to call
Unicode APIs.

-----Original Message-----
From: ace-users-bounces at cse.wustl.edu
[mailto:ace-users-bounces at cse.wustl.edu] On Behalf Of Stew Paddaso
Sent: Wednesday, July 18, 2007 2:03 PM
To: 'Douglas C. Schmidt'; ace-users at cse.wustl.edu
Subject: Re: [ace-users] ACE_TCHAR use in ACE_OS

Thanks for the quick response!

Is there any opposition to a patch that adds the "unified" version of
ACE_OS functions (probably just inlines the desired version of the
function)?  There's a possibility we may be interested in developing
such a
patch in the future.

-----Original Message-----
From: Douglas C. Schmidt [mailto:schmidt at dre.vanderbilt.edu] 
Sent: Wednesday, July 18, 2007 10:45 AM
To: stew.paddaso at gmail.com; ace-users at cse.wustl.edu
Subject: Re: [ace-users] ACE_TCHAR use in ACE_OS

Hi Stew,

>I noticed that certain functions in the ACE_OS namespace mix char,
>and ACE_TCHAR. 


> For example, there are 2 versions of fopen:
>FILE* fopen (const char *filename, const ACE_TCHAR *mode);
>FILE* fopen (const wchar_t *filename, const ACE_TCHAR *mode);
>Why is this?  Why isn't there a single fopen function defined as:
>FILE* fopen (const ACE_TCHAR *filename, const ACE_TCHAR *mode);

Because some early sponsors of ACE wide character support wanted to be
able to have "mixed" wide/narrow strings in the same program!

Take care,

Dr. Douglas C. Schmidt                       Professor and Associate
Electrical Engineering and Computer Science  TEL: (615) 343-8197
Vanderbilt University                        WEB:
Nashville, TN 37203                          NET:
d.schmidt at vanderbilt.edu

ace-users mailing list
ace-users at mail.cse.wustl.edu

More information about the Ace-users mailing list