Re: Calling conventions

Betov wrote:
"James Daughtry" <mordock32@xxxxxxxxxxx> écrivait
news:1143998644.939028.183220@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:

If I understand you correctly, yes.

I may rephrase like this:

If you have a Function that takes no parameter on input,
why on earth would you want to not make it a regular call?

I already explained that. I would much rather have a macro that doesn't
silently change the behavior of my program for a case that really
shouldn't make any difference.

Now, the other point is:

Does there exist one example of such "C call convention", for
a function, that would either take no parameter on input, as
well as one (or more) parameter(s)?

No. There are functions that take no parameters, and there are
functions that take one or more parameters. But none that take zero or
more parameters that I know of.

Even though i never used any of these Functions in my own works,
i think there do exist some, that take, for example, either 3
or 4 parameters. But does there exist, at least, one, that would
take either 0 or 1 parameter?

If yes, i can improve the "C_Call" macros to assume such a
case, but if there is none, even though i am used to work
for free, i am not used to work for nope.

:))

I think I'll just go ahead and use my own fix, thanks. Since I'm
probably the only one who finds a use for this macro, it would be a
waste of your talents to improve it.

.

Quantcast