Products beginning with the letter "I"
-
Like Interacx. The problem is, if I create a class like
IXFoobaz, it looks like an interface, what with that leading I. And then if the last letter is and X and you abbreviate like I did above, then a class (which I actually have) calledIXXmlContainerjust starts to look gawdawful and confusing. Especially since the class implementsIXmlContainer, which is, you guessed it, an interface. :sigh: Marc -
Like Interacx. The problem is, if I create a class like
IXFoobaz, it looks like an interface, what with that leading I. And then if the last letter is and X and you abbreviate like I did above, then a class (which I actually have) calledIXXmlContainerjust starts to look gawdawful and confusing. Especially since the class implementsIXmlContainer, which is, you guessed it, an interface. :sigh: MarcUmmm - isn't that what namespaces are for, rather than using a product specific prefix? Then you could have
Interacx::Foobaz... -
Like Interacx. The problem is, if I create a class like
IXFoobaz, it looks like an interface, what with that leading I. And then if the last letter is and X and you abbreviate like I did above, then a class (which I actually have) calledIXXmlContainerjust starts to look gawdawful and confusing. Especially since the class implementsIXmlContainer, which is, you guessed it, an interface. :sigh: MarcSurely your interfaces would be prefixed II then?
Deja View - the feeling that you've seen this post before.
-
Ummm - isn't that what namespaces are for, rather than using a product specific prefix? Then you could have
Interacx::Foobaz...Stuart Dootson wrote:
Ummm - isn't that what namespaces are for, rather than using a product specific prefix?
Indeed it is. But in this case, the classes in question are controls and I want to differentiate them from the .NET controls. Like how Infragistics prefixes its controls with "Ultra", I'm prefixing my controls with "IX". Marc
-
James R. Twine wrote:
Because XML is correctly written as "XML" and not "Xml."
Well, as far as my coding standards go, I try to adhere to first letter caps, all other letters lowercase, even for abbreviations and acronyms, even though I realize this goes against the standard. But it does avoid things like:
class XMLIDGUIDMapwhich I would write as:class XmlIdGuidMapMarcMarc Clifton wrote:
class XmlIdGuidMap
becomes:
class XIGMbut then, in your standard:class XiGmthat is, for acronym fans:class XGbut, again, your way imposes:class Xgso call itclass Xand don't bother about anymore. :)If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke -
Stuart Dootson wrote:
Ummm - isn't that what namespaces are for, rather than using a product specific prefix?
Indeed it is. But in this case, the classes in question are controls and I want to differentiate them from the .NET controls. Like how Infragistics prefixes its controls with "Ultra", I'm prefixing my controls with "IX". Marc
Marc Clifton wrote:
I'm prefixing my controls with "IX".
So prefix them with Nine.
Deja View - the feeling that you've seen this post before.
-
Marc Clifton wrote:
I'm prefixing my controls with "IX".
So prefix them with Nine.
Deja View - the feeling that you've seen this post before.
Pete O'Hanlon wrote:
So prefix them with Nine.
:laugh: Good one! Marc
-
Gary Wheeler wrote:
This kind of Ares[^]? Well, at least you're not using hydrazine for cream...
yup, see that tiny rocket at the top? We've got the test contract locally. They will be testing the escape system here even to the point of not only simulating, but also executing a full scale destructive failure and attempting an escape just ahead of the explosion. We're talking live action, edge of the seat, Die hard 2 ejection seat ahead of the explosion, fun... unmanned of course with a dozen or more cameras whirring on at extreme high speed taking in all the detail. I can't wait... :-D oh... and I googled this[^] :laugh: :laugh:
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
I guess Trip Tucker's Warp Plasma Blend is out then...
WE ARE DYSLEXIC OF BORG. Refutance is systile. Your a$$ will be laminated. There are 10 kinds of people in the world: People who know binary and people who don't.
-
James R. Twine wrote:
Because XML is correctly written as "XML" and not "Xml."
Well, as far as my coding standards go, I try to adhere to first letter caps, all other letters lowercase, even for abbreviations and acronyms, even though I realize this goes against the standard. But it does avoid things like:
class XMLIDGUIDMapwhich I would write as:class XmlIdGuidMapMarc -
Surely your interfaces would be prefixed II then?
Deja View - the feeling that you've seen this post before.
II, cap'n!
-
dnh wrote:
InteracxXmlContainer
Because XML is correctly written as "XML" and not "Xml." Peace!
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFilesNot according to contemporary naming conventions for C#.
Pits fall into Chuck Norris.
-
Id isn't an acronym, and shouldn't be capitalised anywhere, unless you consider my alternate take that it actually is an acronym, for Identification Datum.
Pits fall into Chuck Norris.
-
Yep - you can ask the right person, or not. :) Peace!
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles -
Not according to contemporary naming conventions for C#.
Pits fall into Chuck Norris.
...And THAT makes strike #4762 against C#... :) Peace!
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles -
...And THAT makes strike #4762 against C#... :) Peace!
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFilesI like it. I like concatenated names, not underscores, so the lower case letters tell me it's all one term, not a single letter for each of three terms.
Pits fall into Chuck Norris.