«

I'm getting the following error:

'strlen' : cannot convert parameter 1 from 'class CString' to 'const char *'

when I try to compile the following code:

HRESULT AnsiToUnicode(CString pszA, LPOLESTR* ppszW)
{
ULONG cCharacters;
DWORD dwError;
// If input is null then just return the same.
if (NULL == pszA)
{
*ppszW = NULL;
return NOERROR;
}
// Determine number of wide characters to be allocated for the
// Unicode string.
cCharacters = strlen(pszA)+1; <-------------------------
..........................
}

Any suggestions as to what the problem might be?

Fausto

Fausto Lopez wrote:
> I'm getting the following error:
>
> 'strlen' : cannot convert parameter 1 from 'class CString' to 'const char *'
>
> when I try to compile the following code:
>
> HRESULT AnsiToUnicode(CString pszA, LPOLESTR* ppszW)
> {
> ULONG cCharacters;
> DWORD dwError;
> // If input is null then just return the same.
> if (NULL == pszA)
> {
> *ppszW = NULL;
> return NOERROR;
> }
> // Determine number of wide characters to be allocated for the
> // Unicode string.
> cCharacters = strlen(pszA)+1; <-------------------------
> .........................
> }
>
> Any suggestions as to what the problem might be?
>
> Fausto
>
>

CString is not a part of the C++ language.
Many string classes have a method to convert to and
from C-Style strings. If you were using the std::string
class, you would use the std::sting::c_str() method.
See if the CString class has a similar method.

--
Thomas Matthews

C++ newsgroup welcome message:
http://www.slack.net/~shiva/welcome.txt
C++ Faq: http://www.parashift.com/c++-faq-lite
C Faq: http://www.eskimo.com/~scs/c-faq/top.html
alt.comp.lang.learn.c-c++ faq:
http://www.raos.demon.uk/acllc-c++/faq.html
Other sites:
http://www.josuttis.com -- C++ STL Library book

Fausto Lopez wrote:

> I'm getting the following error:
>
> 'strlen' : cannot convert parameter 1 from 'class CString' to 'const char
*'

Try http://groups.google.com to find a group qualified to discuss CString.
This group can only reliably discuss platform neutral C++.

> when I try to compile the following code:
>
> HRESULT AnsiToUnicode(CString pszA, LPOLESTR* ppszW)
> {

Oookay. Nobody uses Hungarian Notation anymore. But "psz" means "pointer to
zero terminated string". This Department of Redundancy Department worked in
C using untypesafe conventions. CString is an object.

> ULONG cCharacters;
> DWORD dwError;
> // If input is null then just return the same.
> if (NULL == pszA)

This code treats pszA as a pointer, not an object. Try pszA.IsEmpty().

> {
> *ppszW = NULL;
> return NOERROR;
> }
> // Determine number of wide characters to be allocated for the
> // Unicode string.
> cCharacters = strlen(pszA)+1; <-------------------------

What's wrong with pszA.GetLength()?

I don't know what's wrong with pszA.operator LPCTSTR(), but you don't need
it. You could use a little more learning about both C++ and the MS library
supplying CString.

Also, MFC sucks, but you don't seem to be using all of it. Try WTL.

--
Phlip
http://industrialxp.org/community/bi...UserInterfaces

Fausto Lopez wrote:
> I'm getting the following error:
>
> 'strlen' : cannot convert parameter 1 from 'class CString' to 'const char *'
>
> when I try to compile the following code:
>
> HRESULT AnsiToUnicode(CString pszA, LPOLESTR* ppszW)
> {
> ULONG cCharacters;
> DWORD dwError;
> // If input is null then just return the same.
> if (NULL == pszA)
> {
> *ppszW = NULL;
> return NOERROR;
> }
> // Determine number of wide characters to be allocated for the
> // Unicode string.
> cCharacters = strlen(pszA)+1; <-------------------------
> .........................
> }
>
> Any suggestions as to what the problem might be?

Nope. CString (IIRC) has 'operator const char*' defined, so it
should be picked up for the conversion.

Unfortunately, any more detail on this is off-topic here since
none of MFC classes are part of standard C++. Try the newsgroup
microsoft.public.vc.mfc or comp.os.ms-windows.programmer.tools.mfc

Victor

Phlip wrote:

> Fausto Lopez wrote:

> > // Determine number of wide characters to be allocated for the
> > // Unicode string.
> > cCharacters = strlen(pszA)+1; <-------------------------

> I don't know what's wrong with pszA.operator LPCTSTR()...

There I go not reading the comments again...

If you have _UNICODE turned on then pszA has operator LPCWSTR(), and you
need MS Windows's private lstrlen() function.

But first clean up your attrocious style, and many problems like that will
just go away.

--
Phlip
http://industrialxp.org/community/bi...UserInterfaces

Juha Kettunen wrote:
>
> Phlip wrote:

> > Also, MFC sucks,
>
> Why is that?
> I have been using it many years with now real problems.

When asked why I declare something sucks, I often point to issues writing
unit tests for it.

Such issues are typically symbolic of more important coupling issues.

In MFC, you can't create a window without coupling it, at run-time, to your
entire application. That breaks the principle "Test Isolation".

Try WTL to see what you have been missing.

--
Phlip
http://industrialxp.org/community/bi...UserInterfaces

"Phlip" <> wrote in message
news:5lCIc.1557$ ...
> Also, MFC sucks,

Why is that?
I have been using it many years with now real problems.

On Mon, 12 Jul 2004 22:06:04 GMT, "Juha Kettunen" <>
wrote:

>
>"Phlip" <> wrote in message
>news:5lCIc.1557$ m...
>> Also, MFC sucks,
>
>Why is that?
>I have been using it many years with now real problems.

MFC is a rather thin layer over Win32; it doesn't use proper object
oriented design. Obviously, it's perfectly usable in the same way that
Win32 is. However code using it is not as concise, understandable,
maintainable nor flexible as it that using better frameworks. Check
out almost any more recent GUI framework for better ways of doing
things.

Tom

tom_usenet wrote:

> On Mon, 12 Jul 2004 22:06:04 GMT, "Juha Kettunen" <>
> wrote:
>
>
>>"Phlip" <> wrote in message
>>news:5lCIc.1557$ om...
>>
>>>Also, MFC sucks,
>>
>>Why is that?
>>I have been using it many years with now real problems.
>
> MFC is a rather thin layer over Win32; it doesn't use proper object
> oriented design.

Also it is designed around the capabilities of the C++ compilers of the
early nineties. So essentially C with classes; no templates, no
exceptions, no standard library...etc. Hence many ugly macro hacks.

--
Peter van Merkerk
peter.van.merkerk(at)dse.nl

In message <>, Peter van Merkerk
<> writes
>tom_usenet wrote:
>
>> On Mon, 12 Jul 2004 22:06:04 GMT, "Juha Kettunen" <>
>> wrote:
>>
>>>"Phlip" <> wrote in message
>>>news:5lCIc.1557$. com...
>>>
>>>>Also, MFC sucks,
>>>
>>>Why is that?
>>>I have been using it many years with now real problems.
>> MFC is a rather thin layer over Win32; it doesn't use proper object
>> oriented design.
>
>Also it is designed around the capabilities of the C++ compilers of the
>early nineties. So essentially C with classes; no templates, no
>exceptions, no standard library...etc. Hence many ugly macro hacks.
>
As opposed to, say, ATL, which is designed around the capabilities of a
certain (allegedly-)C++ compiler of the later nineties ;-(

--
Richard Herring