I end up having to remember what the macro is and substitute it in my head as I read. That seems to reflect poorly on the naming of the macros. I would assume you wouldn’t have to emulate the preprocessor if it were a log_function_entry() macro. The ones that I have encountered that were intuitive … Read more
PRIu64 is a format specifier, introduced in C99, for printing uint64_t, where uint64_t is (from linked reference page): unsigned integer type with width of … 64 bits respectively (provided only if the implementation directly supports the type) PRIu64 is a string (literal), for example the following: printf(“%s\n”, PRIu64); prints llu on my machine. Adjacent string … Read more
Back in the olden days of really, really early C, there was no such thing as a prototype. Function argument lists came after the function’s parentheses, like this: square(x) int x; { int y = x * x; return y; } These days, of course, the arguments go inside the parentheses: square(int x) { int … Read more
gcc -E file.c or g++ -E file.cpp will do this for you. The -E switch forces the compiler to stop after the preprocessing phase, spitting all it’s got at the moment to standard output. Note: Surely you must have some #include directives. The included files get preprocessed, too, so you might get lots of output. … Read more
I discovered X-macros a couple of years ago when I started making use of function pointers in my code. I am an embedded programmer and I use state machines frequently. Often I would write code like this: /* declare an enumeration of state codes */ enum{ STATE0, STATE1, STATE2, … , STATEX, NUM_STATES}; /* declare … Read more
This allows you to override the macros when you’re compiling: gcc -DMACRONAME=value The definitions in the header file are used as defaults.
Suppose you had a macro q that ran (and remained) on a single line. Then you could run it on every line in your selection with: :'<,’>normal @q (if you already have a group of lines selected, hitting : produces :'<,’> on the command line) For example, the following macro capitalizes every word but the … Read more
Personally I would do VG:normal @x Edit: changed register to the one you specified.
Two options. First, escape the quotation marks so the shell doesn’t eat them: gcc -Dname=\”Mary\” Or, if you really want -Dname=Mary, you can stringize it, though it’s a bit hacky. #include <stdio.h> #define STRINGIZE(x) #x #define STRINGIZE_VALUE_OF(x) STRINGIZE(x) int main(int argc, char *argv[]) { printf(“%s”, STRINGIZE_VALUE_OF(name)); } Note that STRINGIZE_VALUE_OF will happily evaluate down to … Read more
Jinja2 has no support for comments within a {{ … }} statement. You can only use comments outside of such statements, and then only with {# .. #} or ## comment. {# .. #} is only meant for disabling part of a template or adding comments outside of other Jinja2 syntax. You can’t nest these. … Read more