Hi all,
I have read the documentation of Pepsi & other papers related
(e.g. I know the pepsi documentation says that it has not
been tested on M$), now I am trying to build idc compiler under
windows platform to make some work on it (the sourcecode I've
read looks portable)...
I am trying to build the idc (using the sources in boot folder)
with msdev v6.0 and the first errors reported while compiling
are related to include files for *nix e.g. in file "_object.o.c" :
#include <unistd.h>
...
#include <sys/time.h>
...
#include <sys/param.h>
I have commented the includes, and all is ok.
but.... (as usual with C... there is always a "but...")
I have found an error that I do not know how to solve it.
The problem is related with variable argument extension
for message sends.
The definition for _send is
-----------------------------------------------
#define _send(MSG, RCV, ARG...) ({ \
register oop _r= (RCV); \
struct __closure *_c= (struct __closure *)_libid->bind((MSG), _r); \
(_c->method)((oop)_c, _r, _r, ##ARG); \
})
-----------------------------------------------
so, the arguments can be one or more arguments in a list,
and it is defined as a macro.
Unfortunatelly, Microsoft's documentation says that they
not support ellipsis without a comma:
-----------------------------------------------
Microsoft Specific
Microsoft C++ allows the ellipsis to be specified as an argument if the
ellipsis is the first argument and the ellipsis is preceded by a comma.
Therefore, the declaration int Func( int i, ... ); is legal, but int Func(
int i ... ); is not.
END Microsoft Specific
-----------------------------------------------
and the compiler refuses to compile the macro :-(
as usual I must find a way to make the "compiler" happy
Do you know how to solve this problem?
I have tried to add a comma in the definition but it do not solve the
problem (I think it is related with the fact that the define is a macro
and not a function)
error C2010: '.' : unexpected in macro formal parameter list
Any help and/or suggestion about how to solve/avoid the problem
will be really appreciated, because I am very interested in
putting some time on it.
thanks in advance,
Ale.
_______________________________________________
fonc mailing list
[email protected]
http://vpri.org/mailman/listinfo/fonc