The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I may not like or use best practices but I at least consider them (although most people assume I don't), I may have picked a poor example for my case but the point was more, hey there are some good recommendations, even if the vast majority are crap.
And, with regard to string "best-practices" I have since moved away from the "constant".equals(obj) to String.Compare(val1, val2, true [or false]) == 0 which I think is more better considering that maybe one day I may actually have to use multiple language support.
Absolutely, you need to know your options to be able to choose one intelligently and understand the code of others.
Ennis Ray Lynch, Jr. wrote:
Oh, well then I'm a fan of StringComparer.InvariantCultureIgnoreCase.Compare ( string , string ) and it's ilk.
Have a property or parameter of type StringComparer so the caller can provide an appropriate instance to use.
That's not true of all events; certainly not of ones I write.
It wasn't about you; like I said, it's a generalization.
I even write events that return values, because it makes sense to do so for them.
That'd be called a "callback", not an event.
Would it not be an advantage to "define" an event as "something" that passes an EventArgs? Sounds like a simple pattern to me; a pointer to sender, and a pointer to the arguments.
I really dislike Microsoft telling me how I should write my code
Even if they would, you would not listen. I'd recommend to most other people to consider multiple points of view, but not with you*. You have your own view, and sometimes it pays to have YOU tell how I should write my code.
Have a good 2013, I hope to disagree with you* more often.
Yes, but it shouldn't be enforced by the compiler. I wouldn't want the compiler to dictate where I should put whitespace either.
Eddy Vluggen wrote:
"callback", not an event
The syntax says event so that's what it is; but that's really just a type, conceptually it could be a callback. Just as an int could be an ID or an index.
I wouldn't see a need to have two keywords for such similar concepts. Come to think of it, this is really like the difference between functions and procedures -- functions return a value and procedures don't -- some languages (Pascal and VB for instance) make the syntactic distinction and others (C-like languages for instsance) don't, and I agree with the C way of doing it.
As an aside: VB doesn't allow events to have a return value.
Eddy Vluggen wrote:
it pays to have YOU tell how I should write my code
I hope I don't do that. CP is definitely a great place to get many points of view from others with varied experiences.
<voice type="MOB" >I say this thing with the greatest respect</voice>
There has been a lot of grumbling (not alot[^]) about the new Visual Studio 2012. Well I for one think it's great. Previously, it was difficult to understand how users with Color Blindness and other Visual Issues interacted with your application. By removing all colors and highlights from the User Interface, MS has made all users equal. No more will people with better eye sight be allowed to take advantage of a better visual experience. Equality for all!
You know, we joke about this kind of thing but I'm working in a current version of another "development environment"[^] where adding a line of code into a script requires a double-click or drag and drop.
And this thing has certifications and a developer network as well.
Are you sure it "has certifications" and not it is "certified [as insane]"
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
I also complain about the new design, and even posted the list of the links that will make VS2012 look like VS2010. but after a while I like VS2012 better, specially after installing Windows 8. give it some time...
I like the fact that 2012 feels much faster than 2010, but I doubt that's because they made the UI near-monochrome.
That being said, I find it noticeably more difficult to use for two related reasons. One, I'm not a massive user of keyboard shortcuts. I use the frequent ones (saving files, cut/paste lines of code, etc.), but for the stuff I don't use on a daily basis? I'm not filling up my memory buffer with those shortcuts. Which means when I need to do one of those rare things, I have to hunt for an icon on a toolbar. At a resolution of 2560x1440 with my eyesight, color became a major identifying factor for those icons.
It's just as bad, maybe worse than 2010.
So I'm still working with VS 2008 (on windows 8 pro)..
Some features are simply broken/not working in VS 2010-2012.
The loss of productivity when trying to use 2012 is just ridiculous. And believe me, I tried hard, and still try on occasion; but always end up doing internet searches to find out WHY those features don't work.
Mainly Edit & Continue, which lost all it's purpose from 2010 and up.
I find 2012 to be tolerable now. Once I added the theme editor extension, removed the loud menus, and added a couple extensions that I've long been dependent of in VS2010. Basically, made 2012 act and feel a little more like 2010..
As mentioned, the SQL integration is convenient. The other little touches and improvements to intellisense are welcome. The bland icons with their afterthought colors I could live without but it's not nearly the nails on a chalkboard that the loud menus became for me. The icons aren't as lame when your not blasted with screenfuls of drab grays and white.
Once you get past the distraction of all the GUI changes made for their own agenda for our own benefit, I accept it as a fair toolbox upgrade for writing code for the next dead in 2-5 years technology. It has worked well for my projects so far and I've mitigated most of the my productivity killing distractions. I look forward
I still see it as change for the sake of change from the softies. The Windows, Office, Mobile teams all got drastic UI changes (for better or worse) so the VS team I'm sure was pressured to change.. Too bad that's the best they could come up with. VS2016 will just be the re-branded version of TouchDevelop.