I'm looking for a way to convert a preprocessor token to a string.
Specifically, I've somewhere got:
#define MAX_LEN 16
and I want to use it to prevent buffer overrun:
char val[MAX_LEN+1]; // room for \0
sscanf(buf, "%"MAX_LEN"s", val);
I'm open to other ways to accomplish the same thing, but standard library only.
see http://www.decompile.com/cpp/faq/file_and_line_error_string.htm specifically:
#define STRINGIFY(x) #x
#define TOSTRING(x) STRINGIFY(x)
#define AT __FILE__ ":" TOSTRING(__LINE__)
so your problem can be solved by doing sscanf(buf, "%" TOSTRING(MAX_LEN) "s", val);
I found an answer online.
#define VERSION_MAJOR 4
#define VERSION_MINOR 47
#define VERSION_STRING "v" #VERSION_MAJOR "." #VERSION_MINOR
The above does not work but hopefully illustrates what I would like to do, i.e. make VERSION_STRING end up as "v4.47". To generate the proper numeric form use something like #define VERSION_MAJOR 4
#define VERSION_MINOR 47
#define STRINGIZE2(s) #s
#define STRINGIZE(s) STRINGIZE2(s)
#define VERSION_STRING "v" STRINGIZE(VERSION_MAJOR) \
"." STRINGIZE(VERSION_MINOR)
#include
It's been a while, but this should work:
sscanf(buf, "%" #MAX_LEN "s", val);
If not, it'll need to "double expansion" trick:
#define STR1(x) #x
#define STR(x) STR1(x)
sscanf(buf, "%" STR(MAX_LEN) "s", val);
#
only stringizes macro arguments and the first line is not in the body of a macro.
You should use the double-expansion stringification macro trick. Or just have a
#define MAX_LEN 16
#define MAX_LEN_S "16"
char val[MAX_LEN+1];
sscanf(buf, "%"MAX_LEN_S"s", val);
and keep it in sync. (That's a bit of a bother, but as long as the definitions are right next to each other, you'll probably remember.)
Actually, in this particular case, wouldn't strncpy
suffice?
strncpy(val, buf, MAX_LEN);
val[MAX_LEN] = '\0';
If it were printf
, though, this would be easier:
sprintf(buf, "%.*s", MAX_LEN, val);
While some of the above "work", personally I'd recommend just using a simple string API instead of the dreck that comes in libc. There are a number of portable APIs, some of which are also optimized for ease of inclusion in your project ... and some like ustr have tiny space overhead and support for stack variables.
My two cents. In my example the format to generate is %16s%16s%d
#include <iostream>
#define MAX_LEN 16
#define AUX(x) #x
#define STRINGIFY(x) AUX(x)
int main() {
char buffer[] = "Hello World 25";
char val[MAX_LEN+1];
char val2[MAX_LEN+1];
int val3;
char format[] = "%" STRINGIFY(MAX_LEN) "s" "%" STRINGIFY(MAX_LEN) "s" "%d";
int result = sscanf(buffer, format, val, val2, &val3);
std::cout<< val << std::endl;
std::cout<< val2 << std::endl;
std::cout<< val3 << std::endl;
std::cout<<"Filled: " << result << " variables" << std::endl;
std::cout << "Format: " << format << std::endl;
}
https://i.stack.imgur.com/ETlfv.png
Success story sharing
"%" "MAX_LEN" "%"
a second macro causes the token value to be pasted, e.g.,"16"
because theTOSTRING
macro makes the final code equivalent toSTRINGIFY(16)
.