{"id":3986,"date":"2020-02-15T00:01:12","date_gmt":"2020-02-15T08:01:12","guid":{"rendered":"https:\/\/c-for-dummies.com\/blog\/?p=3986"},"modified":"2020-02-08T08:36:33","modified_gmt":"2020-02-08T16:36:33","slug":"yet-another-oddball-token-paste","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=3986","title":{"rendered":"Yet Another Oddball: Token Paste"},"content":{"rendered":"

I’m constantly on the prowl for obscure and seldom-used C language functions and techniques. One I just discovered — despite coding in C for decades — is the token paste operator. It’s a weirdo.
\n
\nGoing back to the original K&R (“the manual”), the token paste operator isn’t mentioned. No, you must go to the second edition of K&R, published 10 years later in 1988, to discover the ##<\/code> preprocessor operator. Even then, the book is vague on specifics or explaining situations where the operator is handy or even necessary.<\/p>\n

The token paste operator glues two preprocessor varibles together. Also called the pasting operator<\/em>, it’s used in a #define<\/code> directive.<\/p>\n

As a review, #define<\/code> creates a defined constant, a token that can be used throughout the source code file:<\/p>\n

#define SIZE 15<\/code><\/p>\n

The defined constant SIZE<\/code> is changed to 15 before the code compiles. This constant is available to all functions in the file, whereas a constant integer const int size=15;<\/code> would be available only within the function where it’s declared. (Also, const int size<\/em> is a variable and SIZE<\/code> is replaced before compiling.)<\/p>\n

The token paste operator finds its place in those macro constructions that emulate a function. A common example is putchar()<\/em>, though this macro doesn’t use the token paste operator:<\/p>\n

#define putchar(a) putc(a,stdout)<\/code><\/p>\n

The putchar()<\/em> “function” is really a macro, defined in the stdio.h<\/code> header file similar to above, where the putc()<\/em> function does the actual work. Variable a<\/code> is lifted from putchar(a)<\/code> and set into the putc()<\/em> function as its first argument. This is one way #define<\/code> directives build macros.<\/p>\n

The token paste operator works on the macro’s argument(s). It pastes or glues one argument to another or to a constant value. Here’s an example:<\/p>\n

#define paste(a,b) a##b<\/code><\/p>\n

Given arguments a<\/code> and b<\/code>, the paste()<\/em> macro sticks them together as ab<\/code> in your code. So paste(p,i)<\/code> results in pi<\/code>:<\/p>\n

\r\n#include <stdio.h>\r\n\r\n#define paste( a, b ) a##b\r\n\r\nint main()\r\n{\r\n    float pi = 3.141;\r\n\r\n    printf(\"%f\\n\",paste(p,i));\r\n\r\n    return(0);\r\n}<\/pre>\n
In the printf()<\/em> statement, paste(p,i)<\/code> sticks the letters p<\/code> and i<\/code> together to form pi<\/code>. This evaluation becomes float<\/em> variable pi<\/code>, which is output when the program runs.<\/p>\n
Here’s another, more interesting but still questionably useful example:<\/p>\n
\r\n#include <stdio.h>\r\n\r\n#define s1 \"Goodbye, \"\r\n#define s2 \"cruel world!\"\r\n\r\n#define output(x) s##x\r\n\r\nint main()\r\n{\r\n    printf(\"%s%s\\n\",\r\n            output(1),\r\n            output(2)\r\n          );\r\n\r\n    return(0);\r\n}<\/pre>\n
Two defined constants, s1<\/code> and s1<\/code>, are created. The output()<\/em> macro prefixes letter s<\/code> to its argument x<\/code>. So output(1)<\/code> expands to s1<\/code> and output(2)<\/code> becomes s2<\/code>. The printf()<\/em> statement outputs the resulting strings:<\/p>\n
Goodbye, cruel world!<\/code><\/p>\n
I confess that these two examples are lifted from other websites where an attempt was made to describe how the token paste operator could perhaps be useful. Trying to find my own, clever demonstration code proved futile. Then again, the ##<\/code> operator is obscure for a reason.<\/p>\n
What would be interesting to me is to unravel how this operator came to be. It wasn’t documented in 1978 when the first K&R book appeared. So what happened between then and 1988 when it appeared in the second edition? Was it borrowed from another programming language? Did something occur in computer history that necessitated the operator? Perhaps we’ll never know.<\/p>\n","protected":false},"excerpt":{"rendered":"
The preprocessor ## operator is one of the most peculiar ones I’ve encountered. Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-3986","post","type-post","status-publish","format-standard","hentry","category-main"],"_links":{"self":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3986","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3986"}],"version-history":[{"count":4,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3986\/revisions"}],"predecessor-version":[{"id":3993,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3986\/revisions\/3993"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3986"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3986"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3986"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}