|
Hi Cedric,
What do you mean univeral question?
regards,
George
|
|
|
|
|
No one knows. I have it on good authority that the answer is 42 however.
Steve
|
|
|
|
|
What do you mean 42?
regards,
George
|
|
|
|
|
No, it is just a popular joke. Did you see the movie "The Hitchhiker's Guide to the Galaxy" ?
42 is the answer to the universal question. But it isn't funny at all if you didn't see the movie 
|
|
|
|
|
I see. I have not seen the movie before. I have a lot of souce codes to read. Could you come back to this question and show me an example of mixed unicode type (wchar_t* and _T) and non-unicode type (char*), just as I mentioned at the beginning of this thread, like,
_stprintf (wchar_t*, _T("%S"), char*);
I just can not imagine that we can mix unicode type and non-unicode type in one statement.
regards,
George
|
|
|
|
|
Thank you Steve!
What means "plain not safe"?
Actually, I like your style. But I am reading and learning programs written by others. So, could you come back to the sample I wrote above to comment whether it is correct to use char* (non-unicode type) as the 3rd parameter of _stprintf? Thank a lot! 
regards,
George
|
|
|
|
|
George_George wrote: What means "plain not safe"?
This is what I had in mind:
char buffer[1];
sprintf(buffer, "The number is %d", 42);
This code will result in a buffer overrun which at best will crash the program and at worst will open up a security flaw will can be exploited.
Steve
|
|
|
|
|
Thank you Steve!
Maybe I have not made myself understood. My question is not whether the buffer (as the 1st parameter) is large enough (suppose it is large enough in this case, I agree with you about the setbacks of this method), my question is that whether I can input char* (non-unicode type) as the 3rd parameter, while the 1st parameter is wchar_t* type and the 2nd parameter is L (constant string) type.
regards,
George
|
|
|
|
|
Yes. Use %S instead of %s.
Steve
|
|
|
|
|
Thanks Stephen,
I have found that %S is used to specify a wide-character string. Could you show me an example of mixed using of unicode type and non-unicode type, in the following format -- without any errors to print out anything?
I just can not imagine why we can mix the use of unicode type (w_char* and _T) and non-unicode type (char*).
_stprintf (wchar_t*, _T"%s", char*)
regards,
George
|
|
|
|
|
|
Thanks Michael!
Suppose that UNICODE macro is define and we can pass char* type parameter to _stprintf? I can not imagine that -- I think it is not safe. Could you show me an example please to show it works to pass char*?
regards,
George
|
|
|
|
|
Now that I looked more closely at your question  I see where the confusion is coming from. %s means a string of TCHARs, so that will change between ANSI and Unicode builds. The ... in a parameter list means "any number of parameters of any type" - it's totally unrelated to the character set you're building with, but the format string does have to take character sets into account:
TCHAR sz[100];
_stprintf(sz, _T("Hello %hs"), "Bob");Note that I used %hs to mean an ANSI string.
--Mike--
Visual C++ MVP 
LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ
|
|
|
|
|
Thank you Mike!
If UNICODE is defined, then in your above example, TCHAR will be wchar_t, _T will be defined as L and "Bob" will still be char* type (non-unicode type). Is that correct?
I am not sure whether your above example will still work if UNICODE is defined since you print a non-unicode type (char*) to a unicode type _T. If your example works, could you show me please?
regards,
George
|
|
|
|
|
|
Hi Mike,
If I correctly understand, you mean debug into sprintf? C runtime library is not an open source provided by Microsoft.
regards,
George
|
|
|
|
|
Hi,
I know the ISO-9660 file format but I'm unble to generate IS0-9660 file system...I don't want to use any CD writing tools or other ISO creation tools for the creation of iso file ie, I have to write the code in vc++ for creating iso file...
Please specify the sites where I'll get the source code or suggest me for the creation of iso file
I'm eagerly waiting for ur valuable suggestions...
Regards,
nag.
|
|
|
|
|
http://vaporcd.sourceforge.net/index.html
Hope that help.
|
|
|
|
|
Hi nguyenvhn,
I'm thankful for ur prompt response...Vaporcd creates the .iso file by reading CD...But I should create the .iso file for any file ie, If i have text file, it should be created as .iso file... It shouldn't be done through drivers as Vaporcd
has done...
I'm waiting for ur response...
Regards,
nag..
|
|
|
|
|
I am invoking an an MFC exe (inside initinstance () if i put cout<< statement , nothing is reflected in dos winndow.Please if you have any suggestions tell me.
|
|
|
|
|
The application that uses cout should be a console based application(uses main not winmain) otherwise it won't show up.
|
|
|
|
|
memory for reference variable will be allocated or not?
if yes,where does the reference variable get
stored( stack or heap)?
Thanks in advance.
Prashanth.v
-- modified at 3:07 Wednesday 3rd May, 2006
|
|
|
|
|
What do you mean exactly ? Post some code to illustrate your question.
|
|
|
|
|
this question asked me in interview.
i donot have any code.
question is
where does the reference variable get
stored(stack or heap)?
Prashanth.v
|
|
|
|
|
a reference is nothing more than a dereferenced pointer.
when you create a reference variable, you create a variable first (before looking at its type), so the program NEED to store it somewhere in memory to keep its information.
TOXCCT >>> GEII power
[VisualCalc 3.0 updated ][Flags Beginner's Guide new! ]
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
