Our client is demanding that we use hyphens and not underscores in tag names. We have pitched our case, one being that the PLC (CLX/CpLx) doesn't allow them and in our minds PLC/SCADA names should match, but they rejected that argument. I understand that Ignition allows hyphens in most places, but I just think it's bad practice and was hoping for some ammunication to streghten our stance. If we are forced to use hyphens, my pitch will be to use in instance names only, not rework all UDTs.
My primary objection to hyphens is that the hyphen is an arithmetic operator. Which means you can't use jython names in scripts that match your tag name. (Also true of most other punctuation.) The underscore is the one punctuation character that is explicitly permitted in variable names in every programming language.
Out of curiosity, what is their argument for hyphens?
I have the same misgivings that Phil has. I understand underscores, but I tend to avoid those too. I want a tag name that I can use as a variable name that is somewhat self documenting. I, like you, want to be able to look at the tag name and know what to look for in the PLC.
Is it more than just tag names? If they want component/container names to follow this practice too, might run into some headaches.
Maybe, still trying to feel the waters. It might just be they are following standards and don't know why. The reason for this post is to try and gather more info to discuss things intelligently and be more than two groups talking over each other.
Give them a project change notice (or similar) and quote a price they will want to avoid.
If you are still in the initial RFQ show them the charge for that and make it substantial for all the issues you will encounter using an arithmatic operator where it doesn't belong.