Click here to Skip to main content
14,299,900 members

ATL / WTL / STL

 
GeneralRe: Unicode and codeproject article Pin
bkelly1328-Feb-15 10:36
memberbkelly1328-Feb-15 10:36 
GeneralRe: Unicode and codeproject article Pin
Daniel Pfeffer28-Feb-15 11:52
professionalDaniel Pfeffer28-Feb-15 11:52 
GeneralRe: Unicode and codeproject article Pin
Richard MacCutchan28-Feb-15 21:22
protectorRichard MacCutchan28-Feb-15 21:22 
GeneralRe: Unicode and codeproject article Pin
Daniel Pfeffer28-Feb-15 22:12
professionalDaniel Pfeffer28-Feb-15 22:12 
GeneralRe: Unicode and codeproject article Pin
Richard MacCutchan28-Feb-15 22:15
protectorRichard MacCutchan28-Feb-15 22:15 
GeneralRe: Unicode and codeproject article Pin
Daniel Pfeffer28-Feb-15 22:19
professionalDaniel Pfeffer28-Feb-15 22:19 
GeneralRe: Unicode and codeproject article Pin
Richard MacCutchan1-Mar-15 1:42
protectorRichard MacCutchan1-Mar-15 1:42 
GeneralRe: Unicode and codeproject article Pin
bkelly131-Mar-15 5:39
memberbkelly131-Mar-15 5:39 
Telemetry data is usually all numbers and all binary. Economy in bandwidth is a primary goal. The only text may be things like software version embedded in some parts. Even then those are treated as binary data and handed off to the display device.

The text part is where I have a "bunch" of Excel code to build configuration files. Some assembly, make that much assembly, is required to translate the vendor telemetry map (describes all the fields of the data) to something directly usable by my application.

When not running in mission mode the app can write copious log files so I can verify what it did and why. Those are all text based for easy reading. Unicode is fine there.

Side note/rant
IRIG (Inter Range Instrumentation Group) defines telemetry standards for all government ranges. A range is a place where things like bombs are dropped and missiles shot. That standard defines bit 1 as being the MSB and bit N being the LSB. It is absolutely backwards so one of tasks of my code it to renumber all the bit fields. But the vendors do not follow the standard anyway. In one telemetry map the LSB is sometimes bit 0 and sometimes bit 1. In almost every word that has bit field definitions they have put a note that says the MSB is numbered as bit 0 or bit 1. They just cannot understand that the need to keep putting that note in there is a not so subtle indicating that they are doing things wrong. Further, they have at least six different formats for describing those bit fields. With 10,000 parameters in a telemetry stream, that becomes a nightmare for writing code to extract the data needed to process the parameters.
End of rant

It appears that when writing text files, Excel VBA code writes Unicode by default. Since Windows is now Unicode based, its seems much better to go with that. I am mostly there, but have not looked at my tokenizer code lately. (Each parameter is written to a text file, one line per parameter and as many as a dozen pieces of data in each line.) This text file must be in text rather than binary because I must be able to read it myself to check for errors.

Other than log files, none of the real time work uses any text operations. I don't care if it takes 10 bytes per character to store the configuration file.

Conclusion
I'll go with Unicode all the way.

Question
What is this deal with this WCHAR in Visual Studio? One of the articles I found said WCHAR is equivalent to wchar_t, then said no more. Ok, but being a guy with sometimes too much self doubt I still wonder: Are they really the same? Is there something subtle I have not noticed? WCHAR stands out a bit more in the declarations, but for advantages, that seems to be about it. Should I go with wchar_t rather than WCHAR?
Thank you for your time
If you work with telemetry, please check this bulletin board: www.irigbb.com


GeneralRe: Unicode and codeproject article Pin
Richard MacCutchan1-Mar-15 6:13
protectorRichard MacCutchan1-Mar-15 6:13 
GeneralRe: Unicode and codeproject article Pin
bkelly131-Mar-15 15:51
memberbkelly131-Mar-15 15:51 
GeneralRe: Unicode and codeproject article Pin
Theo Buys13-Apr-15 4:27
memberTheo Buys13-Apr-15 4:27 
QuestionCAsyncSocket::Connect( (LPCTSTR) m_address, m_port_number ) Pin
bkelly1324-Feb-15 10:50
memberbkelly1324-Feb-15 10:50 
AnswerRe: CAsyncSocket::Connect( (LPCTSTR) m_address, m_port_number ) Pin
Richard MacCutchan24-Feb-15 22:30
protectorRichard MacCutchan24-Feb-15 22:30 
GeneralRe: CAsyncSocket::Connect( (LPCTSTR) m_address, m_port_number ) Pin
bkelly1325-Feb-15 4:32
memberbkelly1325-Feb-15 4:32 
GeneralRe: CAsyncSocket::Connect( (LPCTSTR) m_address, m_port_number ) Pin
Richard MacCutchan25-Feb-15 5:02
protectorRichard MacCutchan25-Feb-15 5:02 
GeneralRe: CAsyncSocket::Connect( (LPCTSTR) m_address, m_port_number ) Pin
bkelly1325-Feb-15 5:07
memberbkelly1325-Feb-15 5:07 
Questionis DLL appropriate Pin
bkelly1313-Dec-14 15:02
memberbkelly1313-Dec-14 15:02 
AnswerRe: is DLL appropriate Pin
Garth J Lancaster13-Dec-14 17:08
professionalGarth J Lancaster13-Dec-14 17:08 
AnswerRe: is DLL appropriate Pin
Richard MacCutchan13-Dec-14 21:24
protectorRichard MacCutchan13-Dec-14 21:24 
GeneralRe: is DLL appropriate Pin
bkelly1314-Dec-14 5:04
memberbkelly1314-Dec-14 5:04 
AnswerRe: is DLL appropriate Pin
Albert Holguin5-Jan-15 6:55
professionalAlbert Holguin5-Jan-15 6:55 
QuestionIssue with CHTMLEditView in CDHTMLDialog Pin
Member 1101896712-Dec-14 3:53
memberMember 1101896712-Dec-14 3:53 
SuggestionRe: Issue with CHTMLEditView in CDHTMLDialog Pin
Richard MacCutchan14-Dec-14 3:04
protectorRichard MacCutchan14-Dec-14 3:04 
GeneralRe: Issue with CHTMLEditView in CDHTMLDialog Pin
Member 110189677-Jan-15 23:22
memberMember 110189677-Jan-15 23:22 
GeneralRe: Issue with CHTMLEditView in CDHTMLDialog Pin
Richard MacCutchan8-Jan-15 0:07
protectorRichard MacCutchan8-Jan-15 0:07 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.