[ace-users] ACE_TCHAR use in ACE_OS

[Stew Paddaso]

Let me clarify: I was suggesting ADDING the unified versions, NOT replacing
the existing ones. 

Regardless, my suggestion doesn't make sense (duh)... if we call fopen with
an ACE_TCHAR for the filename, the compiler will make sure the correct
function version is called. Sorry or any ensuing panic :-)

-----Original Message-----
From: Johnny Willemsen [mailto:jwillemsen at remedy.nl] 
Sent: Wednesday, July 18, 2007 11:21 AM
To: 'Bennett, Patrick'; stew.paddaso at gmail.com; 'Douglas C. Schmidt';
ace-users at cse.wustl.edu
Subject: RE: [ace-users] ACE_TCHAR use in ACE_OS

Hi,

I agree, we also get then a problem with TAO, now you can build TAO in ascii
mode and still use some unicode api's in your own code without problems.

Johnny 

> -----Original Message-----
> From: ace-users-bounces at cse.wustl.edu 
> [mailto:ace-users-bounces at cse.wustl.edu] On Behalf Of Bennett, Patrick
> Sent: Wednesday, July 18, 2007 8:18 PM
> To: stew.paddaso at gmail.com; Douglas C. Schmidt; 
> ace-users at cse.wustl.edu
> Subject: Re: [ace-users] ACE_TCHAR use in ACE_OS
> 
> 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
> the
> ACE_OS functions (probably just inlines the desired version of the
> existing
> 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,
> wchar_t,
> >and ACE_TCHAR. 
> 
> Right.
> 
> > 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,
> 
>      Doug
> -- 
> Dr. Douglas C. Schmidt                       Professor and Associate
> Chair
> Electrical Engineering and Computer Science  TEL: (615) 343-8197
> Vanderbilt University                        WEB:
> www.dre.vanderbilt.edu/~schmidt
> Nashville, TN 37203                          NET:
> d.schmidt at vanderbilt.edu
> 
> _______________________________________________
> ace-users mailing list
> ace-users at mail.cse.wustl.edu
> http://mail.cse.wustl.edu/mailman/listinfo/ace-users
> 
> 
> _______________________________________________
> ace-users mailing list
> ace-users at mail.cse.wustl.edu
> http://mail.cse.wustl.edu/mailman/listinfo/ace-users
>