I've seen it manyh times, but I don't understand what this does.
I would guess that the prototypes enclosed are C functions,
not C++, so the C++ compiler will call them with the C conventions.
That would make sense, but then
1. Couldn't we just put it around eb.p?
We don't really need it in eb.h.
That would let us indent eb.h if we like, and be a bit clearer perhaps.
2. there are a few functions like set_global_property_string
that are C++ functions, but are declared in eb.p, in eb.h,
and inside extern "C"{}.
In fact this one is declared twice, in eb.p and ebjs.p, one inside extern "C"{}
and the other time not.
So I guess I don't know what this does,
and why we seem to get away with using it inconsistently.
Karl Dahlke
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
