Should i use tchar

However, it's best to tend towards the more flexible approach, as it's much easier to define that macro away on a non-windows platform in comparison to going through thousands of lines of code and adding it everywhere in case you need to port some library to windows mobile.

Use whatever string type is most convenient for you when dealing with text processing - this will hopefully be something supporting unicode, but that's up to you. When dealing with file paths, whip up your own custom type instead of using strings. This will allow you OS-independent path separators, will give you an easier interface to code against than manual string concatenation and splitting, and will be a lot easier to adapt to different OSes ansi, ucs-2, utf-8, whatever.

For people who are "i18n from the start up", save yourself the source code space and simply use all of the Unicode functions. Microsoft themselves use L"Hello World" , 'nuff said. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Ask Question. Asked 13 years ago. Active 1 year, 6 months ago. Viewed 41k times. Improve this question. Peter Mortensen 29k 21 21 gold badges 97 97 silver badges bronze badges.

Add a comment. Active Oldest Votes. The short answer: NO. Improve this answer. Gutblender 1, 1 1 gold badge 12 12 silver badges 24 24 bronze badges. Sascha Sascha 1, 2 2 gold badges 9 9 silver badges 10 10 bronze badges.

Surrogate code points were introduced with Unicode 2. I also think that if you choose to be explicit instead of using TCHAR you should be explicit everywhere. Simply put: be consistent. It was a good idea back when it was introduced, but it should be irrelevant in new code. There were no surrogates. Show 1 more comment. That your application doesn't use the Internet Now, this may be a valid assumption for your software, but Community Bot 1 1 1 silver badge.

End of transmission : — 0xCL. When you maintain old code, you obviously have to work with the environment that code is written for. And if you're maintaining an application which relies on TCHAR then it doesn't matter if that was a good decision or not, you're stuck with it.

Aardvark Aardvark 8, 7 7 gold badges 44 44 silver badges 63 63 bronze badges. I doubt that Windows will ever switch to UTF Not only this creates non-portable windows-centric code, which is unacceptable for libraries - even though may be used for the simplest of cases like UI code - it is not efficient even on Windows itself. That's my opinion, anyway. Nick Nick 6, 1 1 gold badge 21 21 silver badges 34 34 bronze badges.

Indeed, that's what will still work when the character encoding is eventually changed ''again''. You prefer code which is explicit in what the character type is, and thus use a type which is sometimes this and sometimes that? Very persuasive. Steven Steven 2, 3 3 gold badges 28 28 silver badges 39 39 bronze badges. It enables applications to automatically route calls and messages, provide automatic responses IVR or chat bots , record conversations etc.

It can be used in a number of scenarios such as a 'contact center' application that distributes incoming calls to an available agent with the right skillset. UCMA applications are managed by running them on application servers that are activated as part of the Skype for Business server deployment.

It enables applications to send and receive messages for that user, read presence for their contacts, etc. It is also possible to create a 'technical account', that doesn't correspond to a real person, and use UCWA in 'headless' server applications but this approach currently has authentication and scalability limitations.

The latter has slightly fewer capabilities right now: - for example, messages can be sent but not received - though this should change soon. Windows, Microsoft applications, and the. NET Framework generally generate characters in form C using normal input methods. For most purposes on Windows, form C is the preferred form.

For example, characters in form C are produced by Windows keyboard input. However, characters imported from the Web and other platforms can introduce other normalization forms into the data stream.

In regards to the file system, normalization is not required - based on the article Naming Files, Paths, and Namespaces. The web site is concerned with presenting the data to the user, the service with checking the integrity of the data. I was going to suggest that you look at a scheduled task and let Windows control when the process runs, but I re-read your question and noted that you wanted the checks to run every couple of minutes.

The overhead of starting the process might be too great in this case - though some experimentation would probably prove this one way or the other. If you use a scheduled task there's also the possibility that you could start the next check before the current one has finished - something you can code for if you're in complete control.

In addition, the characters are stored in an endian-specific format. Both are valid; see the Wikipedia article on Unicode equivalence for more information. Simply, you need to know or pick the encoding that you will be using. Those APIs are just looking to fill a buffer and need to know how much room they have.

Asked 1 Week ago Answers: 5 Viewed 2 times. You should either know what encoding a blob of text is in because you have a specification about it, or you need to parse appropriate meta data like headers or meta tags where the encoding is specified.