Re: [PATCH] tests: import variables for MSVC.

[Roumen Petrov]

Charles Wilson wrote:
> On 9/24/2010 8:06 PM, Roumen Petrov wrote:
> > I would like to propose different macros for export/import of variables
> > in format:
> >
> > #define XXX(type)    decorator_before type decorator_after
>
> Why?  Peter's formula is practically universal in most packages I have
> seen (ncurses is the only exception that springs to mind).  What
> advantage does using an "unusual" decorator structure bring?
>
> It's not as if we're going to, in our demo/test code, start using
> __stdcall decorator_afters, are we?  (Remember that we're only talking
> about how the test code is structured, not how libtool "requires" client
> code to be written.  Clients would still be free if they chose to, to
> use XXX(type) macros).
>
> --
> Chuck

Because "#define XXX(type)    decorator_before type decorator_after" is 
easy to be adapted to every compiler:
- some will accept both :  __export int and int __export
- other only support :  int __export
and so on.

For the define XXX(type) check apache source

Roumen