 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Languages / C++ Libraries / November 2005_wcsnicmp, _mbsnicmp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt __strnicmp.2c_._wcsnicmp.2c_._mbsnicmp.asp is in the Visual Studio .NET section, and similar errors almost surely exist in C++ library documentation in other sections of MSDN. > The arguments and return value of _wcsnicmp are wide-character strings; > those of _mbsnicmp are multibyte-character strings. I think the return value of _wcsnicmp is an int not a wide-character string. I think the return value of _mbsnicmp is an int not a multibyte-character string. >http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt __strnicmp.2c_._wcsnicmp.2c_._mbsnicmp.asp >is in the Visual Studio .NET section, and similar errors almost surely exist [quoted text clipped - 6 lines] >I think the return value of _mbsnicmp is an int not a multibyte-character >string. I think the text just needs "and return value" removing from it. Have you reported it via the Contact Us link on that page? Dave [Norman Diamond:] >>I think the return value of _wcsnicmp is an int not a wide-character >>string. >>I think the return value of _mbsnicmp is an int not a multibyte-character >>string. > > I think the text just needs "and return value" removing from it. Yes. > Have you reported it via the Contact Us link on that page? Sometimes I report things there. Actually in recent years the quality of response from that procedure has improved somewhat, though it's still inadequate. In the past there would often be replies blaming me and saying I should read the documents, or apologizing for inconvenience but saying it's not Microsoft's fault, or no reply at all. In recent years they have indeed improved to admitting that there are errors, but saying that MSDN content is acquired by MSDN so still unlikely to be fixed. Postings in MSDN managed newsgroups usually get a higher quality of response. Also, you can report the problem using the product feedback website: http://lab.msdn.microsoft.com/productfeedback/ The bugs entered there automatically mirror in the internal MS database. It's also easier for you (and other people) to track the status of the bug. Hope this help, and thanks for reporting the problem. Ale Contenti VC++ Libraries Team -----Original Message----- From: Norman Diamond Posted At: Monday, November 14, 2005 4:25 PM Posted To: microsoft.public.dotnet.languages.vc.libraries Conversation: _wcsnicmp, _mbsnicmp Subject: Re: _wcsnicmp, _mbsnicmp [Norman Diamond:] >>I think the return value of _wcsnicmp is an int not a wide-character >>string. >>I think the return value of _mbsnicmp is an int not a multibyte-character >>string. > > I think the text just needs "and return value" removing from it. Yes. > Have you reported it via the Contact Us link on that page? Sometimes I report things there. Actually in recent years the quality of response from that procedure has improved somewhat, though it's still inadequate. In the past there would often be replies blaming me and saying I should read the documents, or apologizing for inconvenience but saying it's not Microsoft's fault, or no reply at all. In recent years they have indeed improved to admitting that there are errors, but saying that MSDN content is acquired by MSDN so still unlikely to be fixed. Postings in MSDN managed newsgroups usually get a higher quality of response.
Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.