OK, 'unspecified' will make it into the new version of the phpxmlrpc lib.
Thanks
Gaetano
> -----Original Message-----
> From: xml-rpc@xxxxxxxxxxxxxxx
> [mailto:xml-rpc@xxxxxxxxxxxxxxx]On Behalf
> Of bryanh@xxxxxxxxxxxxxxxx
> Sent: Friday, August 19, 2005 5:35 PM
> To: xml-rpc@xxxxxxxxxxxxxxx
> Subject: Re: [xml-rpc] extending system.methodsignature
>
>
> >> I suspect it will be commonplace for there actually to be
> restrictions
> >> on what the type may be that are much too complicated to
> be part of a
> >> signature (restrictions enforced by individual method code), so
> >> anything suggesting that the value can truly be of any
> type would be
> >> problematic.
> >
> >Less so for dynamically-typed languages like Perl, Ruby, etc. And
> >definitely more so for statically-typed languages like C or C++ (Java
> >could probably work around this with introspection, but *I*
> don't want
> >to be the sap who has to code it).
>
> There may be some problem with signatures which is less for
> dynamically typed languages, but the one I'm talking about above isn't
> related to that, because I'm talking about a problem in designing a
> decent signature language, not in implementing code that uses it.
>
> Consider a parameter which is a structure consisting of a string
> followed by either one string or from 1 to 3 integers. Imagine what a
> signature syntax that expresses that would look like. And then think
> of all the other similar weird types.
>
> In this case, it is legitimate to declare the type of that parameter
> as "unspecified," because it's too complex to specify in the signature
> language. But it's not legitimate to say "any type" or even "any
> structure," because a structure consisting of three strings would not
> be valid.
>
> Thus my point that it would be better to have a type specifier that
> means "unspecified" than "any" in a signature language.
>
> --
> Bryan Henderson Phone 408-621-2000
> San Jose, California
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/xml-rpc/
<*> To unsubscribe from this group, send an email to:
xml-rpc-unsubscribe@xxxxxxxxxxxxxxx
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|
