strtok, Find the next token in a string

[gunnar66]

Hi I wan't to run my exe program and pass some arguments with the exe file. example: MyProgram.exe "nr1,nr2,nr3,nr4,nr5" This is some of the code: int APIENTRY WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow) { char *token; char seps[] = ","; token = strtok( lpCmdLine, seps ); This works ok in Visual C++, but i would like to do this in Emededd C++. There i get an error: error C2664: 'strtok' : cannot convert parameter 1 from 'unsigned short *' to 'char *' How can I do this right? Thanks!

[GDavy]

try casting your lpCmdLine var to char* strtok( (char*)lpCmdLine, seps ); It seems strange, cuz LPSTR is an ANSI string... Hope this helps you, Davy

[Anonymous]

This works ok Thanks

[jan larsen]

gunnar66 wrote: error C2664: 'strtok' : cannot convert parameter 1 from 'unsigned short *' to 'char *' It seems like you've defined UNICODE (or _UNICODE, I can't remember the definition for compiling for unicode precisely). If thats the case, then LPSTR translates to unsigned short * instead of char *. strtok requires char * parameters, if you intended to use unicode strings, you should use wcstok instead. [EDIT]A GDavy has corrected me, LPSTR should be defined as CHAR * and CHAR should again be defined as char. But if the code you've given us is the same you're using for your embedded version, then somehow LPSTR must be defined as unsigned short *[/EDIT] "After all it's just text at the end of the day. - Colin Davies "For example, when a VB programmer comes to my house, they may say 'does your pool need cleaning, sir ?' " - Christian Graus

[jan larsen]

GDavy wrote: It seems strange, cuz LPSTR is an ANSI string... Not if you are compiling for unicode, then LPSTR is unsigned short *. "After all it's just text at the end of the day. - Colin Davies "For example, when a VB programmer comes to my house, they may say 'does your pool need cleaning, sir ?' " - Christian Graus

[GDavy]

Nono, LPTSTR is a Unicode format (wide char) in UNICODE and ANSI when not compiling for UNICODE LPSTR is always ANSI string (8bit) LPWSTR is always wide char string(16 bit) But I used to be confused by these too.. Greetz, Davy

[jan larsen]

:-O:doh: You're so right. But regardless, it seems that something makes his compiler believe that LPSTR is defined as unsigned short *. "After all it's just text at the end of the day. - Colin Davies "For example, when a VB programmer comes to my house, they may say 'does your pool need cleaning, sir ?' " - Christian Graus