J
Jeff Relf
Hi WHY,
You tapped out: <<
Since there's no way to create a c# method with optional,
or nullable parameters. >>
No sprintf ( char * Format, ... ) ?
You added: <<
And since you can't write an overloaded web method. >>
Could that be true ? I don't believe it.
You asked: <<
Is it possible to edit the WSDL [ .XML file ]
in conjunction with a c# method
to make the parameter optional,
or have a default value at the client consumer ? >>
Perhaps you could emulates sprintf() by parsing
a string that tells you what parameters are on the stack...
What's a stack ? I hear you asking.
It's a dynamic FILO queue, First In Last Out.
You could create a dynamic FILO queue via a dynamic array,
with pointers to the top and the bottom of the stack.
Of course I would use realloc() to manage a dynamic array...
But I think C#'s automatic allocations
could do something similar... perhaps using the VAR type.
You tapped out: <<
Since there's no way to create a c# method with optional,
or nullable parameters. >>
No sprintf ( char * Format, ... ) ?
You added: <<
And since you can't write an overloaded web method. >>
Could that be true ? I don't believe it.
You asked: <<
Is it possible to edit the WSDL [ .XML file ]
in conjunction with a c# method
to make the parameter optional,
or have a default value at the client consumer ? >>
Perhaps you could emulates sprintf() by parsing
a string that tells you what parameters are on the stack...
What's a stack ? I hear you asking.
It's a dynamic FILO queue, First In Last Out.
You could create a dynamic FILO queue via a dynamic array,
with pointers to the top and the bottom of the stack.
Of course I would use realloc() to manage a dynamic array...
But I think C#'s automatic allocations
could do something similar... perhaps using the VAR type.