|
Not really. It still doesn't explain why it's the standard in the first place. That's what I'm trying to userstand. Lots of people use camel case as a naming standard, but no-one seems able to say why it's better than the others.
So, if you were tasked with developing a set of coding standards, and you decided to use camel case for variables, would you be explain to someone the benefits of that over an MFC-style str... or C-style lpsz... convention?
|
|
|
|
|
Dude, I've told you I don't know why it's the standard, probably because they nicked it from Java at a guess. Standards aren't always designed, sometimes they just get adopted and evolve despite being imperfect. Who knows? I would expect Hungarian got dropped due to the better Intellisense handling in Visual Studio at its mainstay 'p_' no longer holding any worth. In short its benefits got outweighed by its clumsiness.
Regards,
Rob Philpott.
|
|
|
|
|
Rob Philpott wrote: I don't know why it's the standard
I'm not asking why it's the standard where you are. You seem to like it as a naming convention. What I'm asking is why you like it. Why do you think it's better than the others?
I may have misinterpreted your opinion of course. You may dislike it as much as I do...
|
|
|
|
|
Actually, it's not something I feel deeply passionate about. Kind of indifferent to it as a choice, kind of like it because it is a standard and I can, for instance, tell what's a type (Pascal) and what's a variable (Camel) at a glance.
Thank God, it's time to go to the pub now (almost)...
Regards,
Rob Philpott.
|
|
|
|
|
How about the MS Naming Guidelines[^]??
Sarchasm : The gulf between the author of sarcastic wit and the person who doesn't get it.
|
|
|
|
|
I sometimes feel alone in this opinion, but I believe that source code readability is a very, very, close second place to code correctness. Anyone else?
"Why look within yourself for THE TRUTH, when you're the one who's confused in the first place?"
Mr. Spackle
|
|
|
|
|
me too. which is why i think LINQ is crap.
|
|
|
|
|
I find LINQ quite readable in most cases.
|
|
|
|
|
StyleCop is meant to be used on user-written source files. Do not use it on auto-generated files
|
|
|
|
|
Hmmm, I always thought StyleCop was intended for the garbage can...
.45 ACP - because shooting twice is just silly ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997 ----- "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
Is that the latest incarnation of FXCOP? Perfect tool if you want lots of criticism of perfectly valid code if so.
Regards,
Rob Philpott.
|
|
|
|
|
No, FxCop and StyleCop are different. StyleCop analyzes your source code, whereas FxCop does static analysis on your compiled assembly. Normally you are supposed to use them together, so they complement each other.
|
|
|
|
|
Oh, ok. In which case, I hate *both* of them.
Regards,
Rob Philpott.
|
|
|
|
|
|
They complement each other, but they certainly don't compliment you. BTW - they work really well in combination with NDepend.
|
|
|
|
|
Pete O'Hanlon wrote: BTW - they work really well in combination with NDepend.
Interesting. Never used NDepend myself though.
|
|
|
|
|
i hate the need for styling in first place.
|
|
|
|
|
I'll admit that I'm not a fan of all styling conventions, and I think when working on the same project as others, it's nice to just stay consistent. But the underscore in variable names is killing me, I didn't think it would bug me so much.
|
|
|
|
|
I don't like style cop unless I am offshoring unthinking work to unthinking developers. True software is written by creative professionals. If I wanted to be micromanaged I would work in a call center.
|
|
|
|
|
So? Edit it. Big fat hairy deal. I delete mine and put that crap in the main file like VS 2002 and 2003 do. Just because I can. 
|
|
|
|
|
I've had my own domain and Web site for years, but I've never been happy with the domain name (too long + difficult to spell). Also, I'm no longer in the Web site design business - I'm focused on database stuff and database apps, so I don't really need a showcase for my work.
Ss it is 'that time of year', I'm strongly considering rationalizing my on-line presence; migrating to a gmail account, dropping the dedicated Web site and smartening up my Facebook and LinkedIn profiles.
Does anyone have any thoughts as to the advisability of this? Do I need to have my own domain name/Web site to look professional? What do you guys do?
|
|
|
|
|
If your Web Site is backed by a well designed Datastore it will still remain as a showcase for your skills.
Henry Minute
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
|
|
|
|
|
Personally I don't see much point in having a website - unless you're trying to demonstrate something. Your own domain is useful though, I've had mine for the last 15 years purely for email purposes. I run Microsoft Exchange these days from home on it (on a Mac Mini of all things) using a static IP address from BT. The benefit of this: the places I work always block gmail/hotmail etc. but don't know about my own webmail URL so I always have access to email at work. Ha!
Regards,
Rob Philpott.
|
|
|
|
|
I maintain a web site just for that - to demonstrate web service, silverlight, and asp.net skills. The server is at my house, so before going on an interview, I can load up whatever I think I'll need to demonstrate, and take my laptop with me just in case they want to see the source code.
.45 ACP - because shooting twice is just silly ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997 ----- "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001
|
|
|
|
|
lol I do the same but mostly cause I like the windows mobile sync and prefer having mail on my own machines rather than in the cloud while still being able to access it via the web when I need to, etc. Shame WM doesn't support multiple exchange profiles though I think that's finally been fixed in WP7.
|
|
|
|