Pieter Conradie wrote> [many rules for config names] > +Rule 1: [no spaces, use underlines] Agreed. I would add *all* non-ascii problematic chars become underline too, or are removed. ie: What about a name like: "O'Conner Chips Are Us"
> +Rule 2: [mfg prefix] Agreed. > +Rule 3: The name used must be as close as possible to the original name > given by > +the manufacturer, including capitalization. > NO. Strongly disagree. All files, lower case. Period, Simple rule, filenames get mangled, names get munged, and by the time things go from system to system (win32/mac/linux) one f-ing letter wrong, and you are hosed. A simple rule of "all lower case" is easier to enforce. > +Rule 4: If a config file covers a range of targets, then the biggest common > +denominator must be used. > +...@example > +/target/Atmel_AT91SAM7S.cfg covers all AT91SAM7Sxxx targets > +...@end example > Agreed, but I like the "xxx" in place of the numbers, see rule 5. > +Rule 5: If a config file is for a specific target, not covered by a generic > +config file, then the full name must be used. > +used. > Disagree, "x" is often universally used as a wildcard. Conventions are good - and getting the names right make a huge impact. Bigger them most think. -Duane _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
