Dear Matthias Fuchs,
In message 200907162224.23377.matthias.fuchs@esd-electronics.com you wrote:
Please find a better description (avoiding "bootstrap"), and then chose a descriptive name.
ccc - config chip|cpu configuration scc - setup chip|cpu configuration wcc - write chip|cpu configuration wcce - write chip|cpu configuration eeprom
Which of these will you still remember after the third glass of beer? ;-)
I am not a friend of long names :-)
Neiter am I. But there are some basic rules for user interface design. Short commands should only be used for "harmless" operations. Long names are OK for critical actions where you better should have your brain online and not only your fingers continue to type something after the brain detached. And short commands should bne used for frequently used commands, while long, self-explaining commands are OK for more exotic operations.
This _is_ a thing that requires attention, and you do not need it frequently - I guess if you run statistics about command usage it will be in the bottom 5% - agreed?
So a long name is perfect.
Something like "config_cpu" or "set_cpu_config" etc. (and the underscore is intentional to make you think twice what you are doing here).
Best regards,
Wolfgang Denk