My take on this would also be that depending on the parameter source, you'd most still likely want to at the least check the type of an input parameter in any case..?
As in, if it's a command line parameter that could be typed in by a user, it would be best to double check type initially in any case, in case they'd misordered the input parameters, and you could then easily do a form of type conversion right at the beginning in any case...?
Jacob Kruger Blind Biker Skype: BlindZA '...fate had broken his body, but not his spirit...'----- Original Message ----- From: "R Dinger" <rrdinger@xxxxxxxxxx>
To: <program-l@xxxxxxxxxxxxx> Sent: Wednesday, October 24, 2012 4:00 AMSubject: [program-l] Re: Python, Passing a parameter as int instead of STR when using the CMD modual?
Hi Al,I would have to experiment, but you may be able to convert the command tail string to numbers in the parseline function or as Jim noted in precmd. I'mnot sure how they would automaticly pass to your function though.An alternative idea is to have a standard helper routine that your functioncalls to convert its tail string in the function. This could be keyed to the function name and have a small footprint. I can give you a short example if you want. In either case don't you have to convert to int or float or something else depending on the parameter? Richard----- Original Message ----- From: "Al Puzzuoli" <alpuzz@xxxxxxxxx>To: "Program L" <program-l@xxxxxxxxxxxxx> Sent: Tuesday, October 23, 2012 3:02 PMSubject: [program-l] Python, Passing a parameter as int instead of STR whenusing the CMD modual? I've begun playing with Python's CMD module, and I now have a functioning command line interface to my program. I was initially perplexed though as I was seeing odd errors when executing many of my methods. Long story short, I realized that this was due to the fact that CMD passes parameters in as strings, and my functions expected ints. It's really not a big deal, I can just convert to int within each method, but it seems there should be a more elegant way to deal with this. Thanks, Al ** To leave the list, click on the immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe] ** If this link doesn't work then send a message to: ** program-l-request@xxxxxxxxxxxxx ** and in the Subject line type ** unsubscribe ** For other list commands such as vacation mode, click on the ** immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq] ** or send a message, to ** program-l-request@xxxxxxxxxxxxx with the Subject:- faq ** To leave the list, click on the immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe] ** If this link doesn't work then send a message to: ** program-l-request@xxxxxxxxxxxxx ** and in the Subject line type ** unsubscribe ** For other list commands such as vacation mode, click on the ** immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq] ** or send a message, to ** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe] ** If this link doesn't work then send a message to: ** program-l-request@xxxxxxxxxxxxx ** and in the Subject line type ** unsubscribe ** For other list commands such as vacation mode, click on the ** immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq] ** or send a message, to ** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
