CString(const char * instr) is bugged. Try

char name[] = “xsi”;
CString myStr(&name);

Application().LogMessage(myStr);

You’ll get a print out like 030328 etc, probably an address. A workaround is use PutAsciiString(&name). That works.

Actually, it works perfectly fine.
Your &name refer to an address in the memory which is an integer value, therefore its the constructor CString::CString(const CValue& in_val) that is called since a CValue object can be implicitly constructed using an integer value.

Try using CString myStr((char*)&name) instead, should work.

Edit: woops, just noticed that I didn’t removed the & in the hurry, sorry for the misconfusion.

Thanks for pointing that out. I’ll try it when I get home. But implicit type conversion is bad practice in a static type language.

Even if that implicit conversion was not there, I don’t think that passing an integer value and hoping that it will be hopefully interpreted as a char pointer is a good practice as well.

Cheers,
Christopher.

I tried CString myStr((char*)&name), and it didn’t work. It still prints out an address. I am not sure what it’s doing internally. It should just work as

char name[] = “stuff”;
CString myStr(name);

Since char arrays are decayed into pointers. I made a mistake to use &name, it doesn’t really make sense in this case. Pointers are typed, char * is not int *, even though they could contain the same value. There shouldn’t be any type confusions or which constructor to call in this case.

Hey, you got me! I just looked at the doc and there is no CString(const char*) constructor...! :)
You probably confused with the one using wchar_t* as input.

CString(const char*) is new in 7.5. I’m going to send an email to softimage support.

Oh, sorry then. I’m still using the 7.0 version.

When I test it out it works fine passing name to the constructor. As you implied above, your initial code passing &name was passing a char**.

your code is wrong.  “name” is already a pointer, why do you take the address of it?

The correct way to use this is

char name[] = “xsi”;
CString myStr(name);

[quote=louisfeng;22817]A workaround is use PutAsciiString(&name). That works. also wrong, there should be no & there

you may be confused by the C language. [B]name [/B]is of type [B]char *[/B]
[B]char name[] = “xsi”;[/B]
is equivalent to
[B]char *name = “xsi”;[/B]
(there is a technical storage difference, but it “name” is the same type in both case)

[quote=luceric;22885]your code is wrong.  “name” is already a pointer, why do you take the address of it?

The correct way to use this is

char name[] = “xsi”;
CString myStr(name);

also wrong, there should be no & there

you may be confused by the C language. [B]name [/B]is of type [B]char *[/B]
[B]char name[] = “xsi”;[/B]
is equivalent to
[B]char *name = “xsi”;[/B]
(there is a technical storage difference, but it “name” is the same type in both case)

Uhh, did you actually try to run this code? Did it actually print out “xsi”? Try this with 7.5 SDK:

And tell me what it prints out.

char [] (array) is certainly not the same type as char *. They are “equivalent” in the sense that functions accepting char * will take char [] because char arrays will *decay* into pointers when passed as parameters. But you certainly can’t assign like below.

So in the first example I gave in the my first post what does &name give you? It’s a pointer to an array. I tried it because passing in the char [] array like CString str(name) did *not* work properly, printing out a number rather than the actual string. So I tried all kinds of variations to pass in this char*, none of them worked properly.

The SDK is bundled with XSI version 7.5.2009.0204.