Print null terminated character array in C

Question

1.00/5 (1 vote)

See more:

iam getting string from driver in following format
\ U s e r s \ a b c \ A p p D a t a\
in char array and i want output like
\Users\abc\AppData\ without loop
can it be possible ?

What I have tried:

fwrite(notification->FileName, sizeof(char), 50, stdout);

Posted 6-Sep-18 20:58pm

srilekhamenon

Updated 6-Sep-18 21:27pm

Add a Solution

Comments

Richard MacCutchan 7-Sep-18 4:46am

printf("%S\n", notification->FileName);
The upper case S assumes the data is Unicode.

srilekhamenon 7-Sep-18 8:36am

iam getting this output
Warning C4477 'printf' : format string '%S' requires an argument of type 'unsigned short *', but variadic argument 1 has type 'UCHAR *'

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2018-09-06T21:27:00

If the data is in the form you show, where each characters from the driver is separated by spaces then no, you can't remove or ignore those without a loop of some from.

But ... are they nulls, or is the driver passing you 16 bit Unicode characters, and you are assuming 7 or 8 bit ASCII? Because if it is - and I'd say it seems likely - then treating the data you receive correctly as Unicode would be a much better solution. I'd start by looking at the driver details and see exactly what it says it gives you - modern kit expects Unicode of one form or another, so it's quite likely that you are just treating it wrongly.