Mandalika's scratchpad | [ Work blog @Oracle | My Music Compositions ] |
Old Posts: 09.04 10.04 11.04 12.04 01.05 02.05 03.05 04.05 05.05 06.05 07.05 08.05 09.05 10.05 11.05 12.05 01.06 02.06 03.06 04.06 05.06 06.06 07.06 08.06 09.06 10.06 11.06 12.06 01.07 02.07 03.07 04.07 05.07 06.07 08.07 09.07 10.07 11.07 12.07 01.08 02.08 03.08 04.08 05.08 06.08 07.08 08.08 09.08 10.08 11.08 12.08 01.09 02.09 03.09 04.09 05.09 06.09 07.09 08.09 09.09 10.09 11.09 12.09 01.10 02.10 03.10 04.10 05.10 06.10 07.10 08.10 09.10 10.10 11.10 12.10 01.11 02.11 03.11 04.11 05.11 07.11 08.11 09.11 10.11 11.11 12.11 01.12 02.12 03.12 04.12 05.12 06.12 07.12 08.12 09.12 10.12 11.12 12.12 01.13 02.13 03.13 04.13 05.13 06.13 07.13 08.13 09.13 10.13 11.13 12.13 01.14 02.14 03.14 04.14 05.14 06.14 07.14 09.14 10.14 11.14 12.14 01.15 02.15 03.15 04.15 06.15 09.15 12.15 01.16 03.16 04.16 05.16 06.16 07.16 08.16 09.16 12.16 01.17 02.17 03.17 04.17 06.17 07.17 08.17 09.17 10.17 12.17 01.18 02.18 03.18 04.18 05.18 06.18 07.18 08.18 09.18 11.18 12.18 01.19 02.19 05.19 06.19 08.19 10.19 11.19 05.20 10.20 11.20 12.20 09.21 11.21 12.22
Let's start with an example. Here is a sample string. It'd be nice to improve readability by splitting it into multiple lines.
const char *quote = "The shepherd drives the wolf from the sheep's for which the sheep thanks the shepherd as his liberator, while the wolf denounces him for the same act as the destroyer of liberty. Plainly, the sheep and the wolf are not agreed upon a definition of liberty.";
Couple of ideas.
Line continuation: split the string anywhere at white space, and end the line with a backslash (\). Repeat until done.
Backslash (\) is the continuation character often referred as backslash-newline.
eg.,
const char *quote = "The shepherd drives the wolf from the sheep's for which \ the sheep thanks the shepherd as his liberator, while \ the wolf denounces him for the same act as the destroyer \ of liberty. Plainly, the sheep and the wolf are not agreed \ upon a definition of liberty.";
The C preprocessor removes the backslash and joins the following line with the current one. This is repeated until all lines are joined. However in the above example, indentation becomes part of the actual string thus a bunch of unwanted whitespaces appear in the final string. Besides, it is not possible to include comments at the end of any of those lines [after the line continuation character] if you ever wanted to. Both of these minor issues can be avoided with string literal concatenation (discussed next).
Compiling the above with Solaris Studio C compiler results in the following output.
The shepherd drives the wolf from the sheep's for which the sheep thanks the shepherd as his liberator, while the wolf denounces him for the same act as the destroyer of liberty. Plainly, the sheep and the wolf are not agreed upon a definition of liberty.
String literal concatenation: split the string anywhere at white space, and end the line with a pair of quotes ("). Start the next line with quotes, and repeat until done.
eg.,
const char *quote = "The shepherd drives the wolf from the sheep's for which " /* dummy comment */ "the sheep thanks the shepherd as his liberator, while " // another dummy comment "the wolf denounces him for the same act as the destroyer " "of liberty. Plainly, the sheep and the wolf are not agreed " "upon a definition of liberty.";
Adjacent string literals are concatenated at compile time. Comments outside the string literals are ignored, and the concatenated string will not include indented whitespaces unless they are within the string literals (delimited by quotes).
Printing the above results in the following output.
The shepherd drives the wolf from the sheep's for which the sheep thanks the shepherd as his liberator, while the wolf denounces him for the same act as the destroyer of liberty. Plainly, the sheep and the wolf are not agreed upon a definition of liberty.
The straight forward approach is to make multiple standard I/O library function calls to write to desired streams.
eg.,
.. fprintf(stdout, "some formatted string"); fprintf(stderr, "some formatted string"); fprintf(filepointer, "some formatted string"); ..
This approach may work well as long as there are only a few occurrences of such writing. However if there is a need to repeat it many times over the lifetime of a process, it can be simplified by wrapping all those function calls that write to different streams into a function so a single call to the wrapper function takes care of writing to different streams. If the number of arguments in the formatted string is not constant or not known in advance, one option is to make the wrapper function a variadic function so that it accepts a variable number of arguments. Here is an example.
The following example writes all messages to the log file, writes only informative messages to standard output (stdout) and writes only fatal errors to the high priority log. Without the logfmtstring()
wrapper function, the same code would have had five different standard I/O library calls rather than just three that the sample code has.
% cat multstreams.c #include <stdio.h> #include <string.h> #include <stdarg.h> FILE *log, *highprioritylog; void logfmtstring(const char *fmtstr, ...) { va_list args; va_start(args, fmtstr); vfprintf(log, fmtstr, args); if (strstr(fmtstr, "[info]") != NULL) { vfprintf(stdout, fmtstr, args); } if (strstr(fmtstr, "[fatal]") != NULL) { vfprintf(highprioritylog, fmtstr, args); } va_end(args); } void some_function(..) { log = fopen("app.log", "w"); highprioritylog = fopen("app_highpriority.log", "w"); ... logfmtstring("[info] successful entries: %d. failed entries: %d\n", completecount, failedcount); logfmtstring("[fatal] billing system not available\n"); logfmtstring("[error] unable to ping internal system at %s\n", ip); ... fclose(log); fclose(highprioritylog); } % cc -o mstreams multstreams.c % ./mstreams [info] successful entries: 52. failed entries: 7 % cat app.log [info] successful entries: 52. failed entries: 7 [fatal] billing system not available [error] unable to ping internal system at 10.135.42.36 % cat app_highpriority.log [fatal] billing system not available %
Web search keywords: C Variadic Functions
It is possible to declare and use variables within the scope of a case
label with one exception -- the first statement after a case
label should be a statement or an expression, but not a declaration. If not compiler throws an error during compilation such as the following.
% cat switch.c #include <stdio.h> int main() { switch(NULL) { default: int cyear = 2015; printf("\nin default .."); printf("\nyear = %d", cyear); } } % cc -V -o switch switch.c cc: Sun C 5.12 SunOS_sparc Patch 148917-08 2014/09/10 acomp: Sun C 5.12 SunOS_sparc Patch 148917-08 2014/09/10 "switch.c", line 6: syntax error before or at: int "switch.c", line 8: undefined symbol: cyear cc: acomp failed for switch.c
The above failure can be fixed by either moving the variable declaration to any place after a valid statement if possible, or by adding a dummy or null statement right after the case
label.
eg.,
1. Move the declaration from right after the case
label to any place after a valid statement.
/* works */ switch(NULL) { default: printf("\nin default .."); int cyear = 2015; printf("\nyear = %d", cyear); }
2. Add a dummy or null statement right after the case
label.
/* works */ switch(NULL) { default: ; // NULL statement int cyear = 2015; printf("\nin default .."); printf("\nyear = %d", cyear); }
3. Yet another option is to define or create scope using curly braces ({}) for the case where variables are declared.
/* works too */ switch(NULL) { default: { int cyear = 2015; printf("\nin default .."); printf("\nyear = %d", cyear); } }
Also see: Keyword – switch, case, default
Labels: C programming tidbits tips
2004-2019 |