How to convert ascii to string

[karthik.datt]

i have written a code on assembler... when we enter the mnemonics it will give opcode... when i use %x in the printf it is giving correct opcode.. but when i use %c or %s it is printing some different characters.. but what i want is if i use %s also then it should give correct opcode... how to do this??

[WaltP]

It depends on how you've defined the OP Codes and the mnemonics.

[karthik.datt]

i used sprintf.... now when i use %s in printf it is printing correctly on console but when i write that to a txt document usung fwrite its not writing correctly...

[karthik.datt]

it is displaying some unknown characters

[Narue]

C isn't any different from assembly in that there's no magic. The byte representation of an integer isn't going to be meaningful when directly displayed as characters. What *printf() does is convert the value to an string representation along the lines of:

/* Very basic, do not use except as a starting template */
while (value != 0) {
    s[i++] = value % base + '0';
    value /= base;
}

Pretty much the same logic you'd use for the operation in assembly.

[WaltP]

OK, it's time for the

[boilerplate_help_info]

Posing requests for help must be well thought out if you want help quickly and correctly.  Your post did not meet the criteria for quality help. You may get some posts, but are they going to be useful?  Check your post with these checkpoints - what is it [i]you[/i] missed:
[list=1]
[*]Ask a question that can be answered. Do not ask
- What's wrong with my code?
- Why doesn't this work?
- Anything else that does not give us useful information
[*]Post your code.  If we don't know what you did, how can we possibly help?
- Use [b]PROPER FORMATTING[/b] -- see this
- Use CODE Tags so your formatting is preserved.
If we can't follow your code, it's difficult to help. We don't care that you're still working on it. If you want us to read it, it must be readable
[*]Explain what the code is supposed to do.  If we don't know where the target is, how can we help you hit it?
[*]Explain what actually happened! If we don't know where the arrow went when you shot it, how can we tell what went wrong and how far from the target you are?
[*]If you have errors, post them! We can't see your screen.  We can't read your mind. You need to tell us what happened.
[*]Do [b]not[/b] ask for code. We are not a coding service. We will help you fix your code. 
    If anyone posts working code for you, they are a cheater. 
    If you use that code [i]you[/i] are a cheater.
[*]Do [b]not[/b] bore us with how new you are. We can tell by your code.
- Do not apologize. We were all new, and unless you are completely 
  brain dead you will get better.
- Do not ask us to "take it easy on you."
- Do not say "I don't know what's going on." That's obvious since
  you posted for help. Use that time wisely by [b]explaining[/b] as best 
  you can so we can help.
[*][b]Do not post your requirements and nothing else. [/b]We view that as a lazy do-nothing student that wants us to do their work for them. That's cheating and we [i]will[/i] be hard on you.
[*]Do not attach files except when absolutely necessary. Most of us are not going to download file.  Add the information to your post.
[*][b]Do not tell us how urgent it is.[/b] Seriously, for us there is no urgency at all. Many that can help will ignore any URGENT or ASAP requests.
[/list]
Think more about your next post so we don't have to play 20 questions to get the info we need to help you.

[/boilerplate_help_info]