You can't get rid of that warning, and it should actually even be
worded more strongly. It is simply not possible to access C-style
varargs parameters at the callee side in FPC (you may be able to hak
using pointers which will work on some platforms, but it will crash
and burn in most cases).
On 12 Nov 2007, at 10:32, Inoussa OUEDRAOGO wrote:
This is the c prototype ( type ) translated, actualy it is a array
of PCHAR.
code taken from apache source
const char *(*take_argv) (cmd_parms *parms, void *mconfig,
int argc, char *const argv[]);
/code
Is the
More importantly then supressing it, which I consider something
unimportant, would be knowing what it means, and if there is some kind
of potential problem it indicates that we are overlooking.
Agree, clarified by Jonas's response .
By the way, have you been able to make a module on ( Linux +
double pointer to char in C). I was indeed wrong about the varargs
stuff I said earlier, for some reason I had read array of pchar as
array of const.
Ok, Thanks.
By the way, h2pas should also be corrected, because it translates
code langage=c
void f(int a, char* p[]);
/code
done : http://www.freepascal.org/mantis/view.php?id=10156
2007/11/12, Marco van de Voort [EMAIL PROTECTED]:
double pointer to char in C). I was indeed wrong about the varargs
stuff I said earlier, for some reason I had read array of pchar as
array of const.
Ok, Thanks.
By the way,
After reconsidering the -n option. It should depend on the -f /
--config= option.
Darius
Darius Blaszijk wrote:
I've been playing around with fpmake again and came to the conclusion
that it exhibits some strange behavior (at least I think so)
The -v option gave me the following fFCl command
The following patch fixes a broken TTarget.Mode.
Darius
Index: src/fpmkunit.pp
===
--- src/fpmkunit.pp (revision 9207)
+++ src/fpmkunit.pp (working copy)
@@ -1206,6 +1208,7 @@
begin
