Andy Dustman wrote:
[snip]
Solution: parse() does have the capability of finding a parameter type (for the above-mentioned reason), i.e. the parameters could be written:
HostId:int DomainId:int Name:nb IP:int
I propose also allowing :optional to follow the type, so that parse() can set this properly, i.e.:
HostId:int:optional DomainId:int:optional Name:nb:optional IP:int:optional
Note that currently default values take precedence over optional values (if it could find any).
I'll prepare a patch that can do this if requested (DC/ZopeCorp decide this is a good solution) and it will also fix the parameter="value" parsing problem (broken in 2.4.0).
This sounds like a good solution. I have worked around this same issue many times myself. -- | Casey Duncan | Kaivo, Inc. | cduncan@kaivo.com `------------------>