There are several pages on the wiki regarding different methods for argument parsing and its cousin, named arguments. This page is for general discussions regarding a potential system that might satisfy both of those. Here we can toss back and forth general design questions, key concerns being: - Which feels the most TCL-like - Which might sacrifice some freedom for power
One that I've been working on here and there uses a prefix notation in the proc definition for the named argument system to know what to do with. For instance:
proc foo { fname o_lname } {
puts "$fname"
}Here, the lname is understood by a wrapping proc to be "switchable", and the proc also understands that fname is a required proc. What do people feel about similar ideas to expand the proc definitions? Another idea is to implement some sort of enumerated definition in the proc "e_actiontype", where actiontype might be defined, maybe within the proc body, or a central location.