🚀 go-pugleaf

devitto@ferndown.ate.slb.com wrote:
: What about Bjarne's idea of "include" as a keyword that only has the effect
: of a #include if the file has not been "include"d already.

I'm okay with it as long as we leave something to mean the old
include-no-matter-what behavior.

A common trick for making an array that includes pointers to functions is
something like:

file1.h --------

func(foo);
func(bar);



file2.cc ------

#define func(x)		int x(char*);
#include <file1.h>
#undef func
#define func(x)		{ ##x, x },

struct funcHandle {
    const char* const          name;
    const int (* const)(char*) function;
} funcArray[] = {
#include <file1.h>
};

--------------

It may be overly clever, but I've seen this one in almost every C/C++ shop
I've worked in.

--
Micha Berger 201 916-0287        Help free Ron Arad, held by Syria 3255 days!
AishDas@haven.ios.com                     (16-Oct-86 -  5-Oct-95)
<a href=news:alt.religion.aishdas>Orthodox Judaism: Torah, Avodah, Chessed</a>
<a href=http://haven.ios.com/~aishdas>AishDas Society's Home Page</a>

[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy is
  summarized in http://reality.sgi.com/employees/austern_mti/std-c++/policy.html
]