Having just gotten burned by nomenclature issues, I want to chime in. Yes, I know this is a dead issue because the concrete’s set.
I bought a shield shield. Nomenclature on the top of the shield is Arduino land talk. The bottom is Photon speak. But I didn’t know that. Pin A5 is totally different depending on which name system you are using.
Programmers write in terms of A5. And when things go wrong and you pick up an oscilloscope, you want to put the probe on something visually labeled A5. Easy to make a mistake. Easy for a hardware guy to lay something out incorrectly. (Remember the Gimli glider near plane crash in Canada? The plane wanted to be refueled in gallons but the fuel guy used pounds. Oops. Ran out of fuel in the air.)
Worse, if I ever had to recode my project for a new chip, I absolutely do not want to have to go in a rename pins. “Find all the references to A5 and change them to …” The base problem is ONE name meaning DIFFERENT things.
This is akin to the human language word problem of ‘gift’ is something nice to get in English but ‘gift’ in German, not so much. (It means poison.)
So call it whatever you want, but don’t introduce ambiguity.
It’s too late to solve the following. My application wants to do one “port read” and grab 8 bits status in one bus transfer. It makes it nice if, for example, port B has pins B1, B2, B3, … B8. The PIC microcontroller does this.