hi there,
when we use the msvcrt.dll printf,
why something line new line doesn't works as expected?

-> using win32ax.inc (btw)

cinvoke printf,'a = %s \r\n b = %s', 'apple', 'boy'

outputs

a = apple \r\n b = boy

why?

Because fasm is not a C compiler! fasm does not "look into" the strings and convert \r things to 0x13 like C does.

Why not define the string manually? You will have much more control over it that way

e.g:

I don't use it myself but it should work.

Also:

But note that printf will expand 10 (\n) into CRLF when used on Windows so you don't need to do it explicitly and better you don't do it that way so you can reuse the code in Linux without any trouble.

i know fasm is not c compiler.
but isn't it the convert task should be done by that particular "function printf()" instead of compiler?

i mean, it is that function job to detects "\n" in the string pointer and do the CRLF itself.. assembler/compiler just pass the string pointer to this function, so.. i don't quite get it when you said compiler does the conversion.

A C compiler converts the backslash (\) escape codes at compile time.

printf converts the percent (%) escape codes at runtime.

ok, i think i get it.
but somehow i found it weird, why c compiler doesn't let printf handles backslash (\) at runtime.

is there any specific reason or it just ... tradition?

Why should it be handled at runtime, if it can be handled once during compilation?

You don't handle at runtime some thing whose result is same on every run. That is wasting of time.