How do you name your spaces?
-
Wrong is evil and must be defeated. - Jeff Ello
"CONSIDER using plural namespace names where appropriate." Never pluralize.
-
"CONSIDER using plural namespace names where appropriate." Never pluralize.
And your reasoning is?
Wrong is evil and must be defeated. - Jeff Ello
-
Try Sander.CatOwner, or Sander.Wood.Smooth perhaps?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
Sander.CatOwner, I like it! Gives a personal touch to my software :laugh:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Sander Rossel wrote:
I'd go for SanderRossel as Sander.Rossel would imply I'd actually have Sander.SomethingElse, which clearly isn't the case.
By your redenation; Rossel.Sander and Rossel.Nika :)
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)
Well, Nika DOES love to sleep behind the computer, just like her owner :D
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
I follow the Java standard for package names, so everything is under
com.vilmos. Actually that's a lie, it's mostly `com.lexa`, but that's because there is a master project called Lexa.veni bibi saltavi
Nagy Vilmos wrote:
there is a master project called Lexa
The #1 Dutch dating site? :omg:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
I use the alphabet. a.b.c etc... j/k CompanyName.SoftwareProjectName.VisualStudioProjectName (ACME.RoadRunner.DAL) or something like that. or SoftwareProjectName.VisualStudioProjectName (RoadRunner.DAL) or something like that.
Slacker007 wrote:
ACME.RoadRunner
Well, at least that ACME stuff crashed about as often as Visual Studio :laugh: :thumbsup:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
"CONSIDER using plural namespace names where appropriate." Never pluralize.
That's a rule for database tables :)
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Wrong is evil and must be defeated. - Jeff Ello
MSDN wrote:
X DO NOT use the same name for a namespace and a type in that namespace.
HATE it when that happens :sigh:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
That's a rule for database tables :)
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
And still a bad idea.
-
That's a rule for database tables :)
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
And it's wrong, well, at least when it comes to standards. The ISO standard says Pluralize.
Wrong is evil and must be defeated. - Jeff Ello
-
And it's wrong, well, at least when it comes to standards. The ISO standard says Pluralize.
Wrong is evil and must be defeated. - Jeff Ello
Some pretty good reasons to singularize[^] :)
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Some pretty good reasons to singularize[^] :)
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
The Joint Technical Committee (ISO/IEC JTC 1, Information technology, Subcommittee SC 32) that develops the SQL Standard has specified that one should follow ISO/IEC_11179[^] for naming. Which states Singular for Columns and Plural for Tables. The point of following standards, even if you don't like the aesthetics, is (amongst others) to minimize ambiguity. The concept behind it is as simple as it gets. A row is singular. A collection of rows is plural. So reason one in your link is just conceptually wrong. Yes, an applebag can contain apples but you don't name the bag "Apple", you name it "Bag". The content that you search are Apples. But I guess that's why you see so many tables following the pattern "tblCustomer". X| And the rest is just opinions. As far as I'm concerned you can do as you want. But if you choose one way, you should stick to it. That's much more important
Wrong is evil and must be defeated. - Jeff Ello
-
Let's say you're starting a new project and you pick your own name (or your company name) as default namespace, how would you do it? In my case: Sander.Rossel or SanderRossel? I'd go for SanderRossel as Sander.Rossel would imply I'd actually have Sander.SomethingElse, which clearly isn't the case. Judging from what I've seen the Sander.Rossel style is the more frequently used though. I've seen both methods and I was wondering which people prefer.
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
Sander Rossel wrote:
which clearly isn't the case at this time
I worked for a company that did something similar. They also had code that carried over from the last company. What happened was the dev team split from the web team into two separate companies. So they kept all their code. They ended up with two namespaces. Not that you're going to clone yourself in this case, but I'm just pointing out it's possible you'd want to have Sander.SomethingElse later on.
Elephant elephant elephant, sunshine sunshine sunshine
-
Sander Rossel wrote:
which clearly isn't the case at this time
I worked for a company that did something similar. They also had code that carried over from the last company. What happened was the dev team split from the web team into two separate companies. So they kept all their code. They ended up with two namespaces. Not that you're going to clone yourself in this case, but I'm just pointing out it's possible you'd want to have Sander.SomethingElse later on.
Elephant elephant elephant, sunshine sunshine sunshine
Well, I have a good friend who's first name is also Sander. If we ever wrote software together we'd have Sander.Rossel and Sander.HisLastName or maybe Sander.JointForces ;p
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
:laugh: I keep wanting to introduce a classed called "BlessedAreTheCheeseMakers" but my line manager won't let me, because of the parent company's audit policies :(
Every day, thousands of innocent plants are killed by vegetarians. Help end the violence EAT BACON
I've always wanted to call my classes: WeAreNowTheKnightsWhoSay-ekki-ekki-ekki-pitang-zoom-boing! Watched it again last night, no really! Just such good good fun!
-
I've always wanted to call my classes: WeAreNowTheKnightsWhoSay-ekki-ekki-ekki-pitang-zoom-boing! Watched it again last night, no really! Just such good good fun!
-
Sean McPoland wrote:
Watched it again last night,
Psychosis at 10 Film at 11 Those who do not remember the past, are doomed to repeat it. Those who do not remember the past, cannot build upon it.
Ain't that the truth, I 'know' it was made in 1975, and I watched it in 1975, but when you put it like that, It's another dimension!
-
Let's say you're starting a new project and you pick your own name (or your company name) as default namespace, how would you do it? In my case: Sander.Rossel or SanderRossel? I'd go for SanderRossel as Sander.Rossel would imply I'd actually have Sander.SomethingElse, which clearly isn't the case. Judging from what I've seen the Sander.Rossel style is the more frequently used though. I've seen both methods and I was wondering which people prefer.
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
