c - Why weren't new (bit width specific) printf() format option strings adoped as part of C99? -

-

How to format string in cross-platform printf () C (research, the number of bits Keeping in mind, I hope every integer argument should be printf () ) The article I ran across discusses non-standard options that are printf () Format string, such as (which seems to be a Microsoft-specific extension) can be passed: 

  printf ("% I32d \ n", my32bitInt );

It states that:

The ISO 99 99 contains inttypes.h header file that contains several macros for use in platform-independent printfaces. Coding

... and then lists a set of macros that can be said in the header. By looking at the header file, I must write to use them: 

  printf ("%" PRId32 "\ n", my32bitInt);

My question is: Am I forgetting something? Is this really the standard C99 method? If so, why? (Although I am not surprised that I have never seen a code which uses the format string in this way, because it looks very cumbersome ...)

The argument is that & lt; Inttypes.h & gt; The current practice is standardization:

& lt; Inttypes.h & gt; was taken from the header of the same name found on several existing 64-bit systems.

But the rest of the text does not write about those macros, and I do not miss that they were doing the exercises on time.

What are the speculation now, but the experience of how the standardization committees work.

An advantage of the C99 macros on the additional format specification standardization for printf (note that C99 also added something) is that & lt; Inttypes.h & gt; and and lt; Stdint.h & gt; When you are already supporting the necessary attributes in an implementation, there is enough typing and writing two files with macros. This reduces the cost of making existing implementation conferences, reduces the risk of breaking existing programs, which uses the use of existing implementation features (does not interfere with standard means) and to close the programs consistent with the implementation Provides those who do not have this header (they can be provided by the program) Additionally, if Yanwyn specific methods were already different, so it is not suitable to apply a second.


Comments

Post a Comment

Popular posts from this blog

c# - ListView onScroll event -

-
I am programming a simple C # application, and I need a Scallow event on the list view. So I inherited the original ListView class created in ListviewEx witch. I found out how to locate the scroll message from WinAPI and I modified the WndProc method. Now I have this WndProc: protected override zero WndProc (Ref message message) {base.WndProc (Ref I); If (m.msg == WM_VSCROLL) {onScroll (This, New EventArgs ()); }} But the problem is, I do not know how to know about scrolling information. This data should be in wParam, but there is a LOWORD macro ++ like in C in C # and I switch to find the criteria like SB_ below, SB_ENDSCROLL, SB_PAGEUP etc. there any way Need to change the LOWORD macro from C #? Or any other way to find the necessary parameters about scrolling? You can define the WParam constants as the following: Private const int WM_HSCROLL = 0x114; Private Constant WM_VSCROLL = 0x115; Private contact int SBHOZZ = 0; Private Consultant SB_VERT = 1; Private Con...
Read more

PHP - get image from byte array -

-
I am trying to create a back-end for my mobile application. I am sending the content of an image in the body of the HTTP request (output stream) as a byte array, I want to read this stream of bytes in PHP scripts and take back an image. Can anyone tell me how can I do this? Thank you. You can obtain the request body $ body = Reading from file_get_contents ('php: // input'); What you do with that data Depending on you, you can write the data in a file as you mentioned that this is image data, you can drop the data into the object can do. Another option is to use and load the image.
Read more

Linux Terminal Problem with Non-Canonical Terminal I/O app -

-
I have a small app written in C to run on Linux. Part of the app accepts user-input from keyboard , And it uses non-canonical terminal mode so that it can respond to each keystroke. The section of the code that accepts input is a simple task that is called repeatedly in the loop: char get_input () {char C = 0; Int res = reading (input_tamille, & amp; c, 1); If (RSS == 0) 0 returns; If (res == -1) {/ * snip error handling * /} return c; } It reads a letter from the terminal if there is no input within a given time limit, (c_cc [VTIME] value in the vocabulary structure), read () 0 And get_input () is called again It all works very well, I have recently discovered that if you run this app in a terminal window, and then the app Close the terminal window without ending, the app will not exit Received, but CPU intensive launches into an infinite loop, where the read () returns 0 without waiting continued. So how can I get out of the apple if it runs from the terminal win...
Read more