Question about many #define

[Alan Pong]

#define PIC1 "pic1.gif"
#define PIC2 "pic2.gif"
:
:
#define PIC999 "pic999.gif"

any shortcut/trick/preprocessor directive/operator can do above easily?

thanks.
rgds.
alan
--END

 

[Owen Jacobson]

#define PIC1 "pic1.gif"
#define PIC2 "pic2.gif"
:
:
#define PIC999 "pic999.gif"

any shortcut/trick/preprocessor directive/operator can do above easily?

What are you really trying to do? What is the problem the above is
attempting to solve?

// Untested, and my macro-fu is seriously weak
#define PIC(x) "pic" #x ".gif"

// Unsure of efficiency of ostringstream, but otherwise better, IMO
#include <string>
#include <sstream>

inline
std::string pic(int x) {
std:stringstream buffer;
buffer << "pic" << x << ".gif";
return buffer.str ();
}

 

[=?ISO-8859-15?Q?Juli=E1n?= Albo]

#define PIC1 "pic1.gif"
#define PIC2 "pic2.gif"
:
:
#define PIC999 "pic999.gif"

any shortcut/trick/preprocessor directive/operator can do above easily?

Write a program that write it.

But I wonder why you need to do that.

 

[Greg Comeau]

#define PIC1 "pic1.gif"
#define PIC2 "pic2.gif"
:
:
#define PIC999 "pic999.gif"

any shortcut/trick/preprocessor directive/operator can do above easily?

You can probably ease it with the preprocessor string'izing operator
(google that) but this leads to the question of "What are you trying
to ease?" That is, why do you need so many define's? How is
it better than just keeping track of some int? Etc.