Norman Walsh wrote:
> The TC discussed this and is considering adding an 'optionalparamdef'
> wrapper instead (i.e., instead of optional above, not instead of paramdef).
>
> Does this seem useful to the community at large?
>
> Is a similar optionalmethodparam element needed for methodparam?
python has some unusual parameter passing rules, too, for example you
can pass a parameter by name such as 'foo(bar=42)'.
Wouldn't it make sense to annotate the 'paramdef' entity with an
attribute that assigns such a type ? That could be any string such as
'optional', 'named' or whatever fits for a given language...
Regards,
Stefan