Strong Typing
-
PIEBALDconsult wrote:
I prefer to have all the declarations in one place (the top) so in C# I still do that by choice.
I hate that. Although it probably doesn't help that most of the functions i see doing it are hundreds of lines long, making it a real chore to track down declarations and ensure variables are being used correctly.
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
Yeah, if you can't the declaration then your method is too big (size matters). On the other hand, if they're all at the top, they're easy to find.
-
John R. Shaw wrote:
Then again I wish C would allow me to declare a variable where ever I wanted
I prefer to have all the declarations in one place (the top) so in C# I still do that by choice. But requiring such isn't very friendly, flexibility is good.
Lol I think I was using C# for about 4 months before I realized I didn't have to do it. Its a tough choice though, all declarations at the top make it much easier for someone to come in and read your code, whereas its easier to code when I can make a variable whenever I need one. You can definitely look at my code and see the days on which I was lazy, because there is nothing in our coding guidelines about where to put variable declarations.
-
PIEBALDconsult wrote:
I prefer to have all the declarations in one place (the top) so in C# I still do that by choice.
Same here, sure beats having to browse through the code looking for the declarations...
Paul Conrad wrote:
browse through the code
But you did know about the existence of the CTRL-F feature of your editor? Or (with any modern IDE) even the context menus 'Go to Declaration' feature? :~
Failure is not an option - it's built right in.
-
Paul Conrad wrote:
browse through the code
But you did know about the existence of the CTRL-F feature of your editor? Or (with any modern IDE) even the context menus 'Go to Declaration' feature? :~
Failure is not an option - it's built right in.
-
"Don't bother with it, waste of time." :wtf:
------------------------------- Carrier Bags - 21st Century Tumbleweed.
breaks keyboards too
-
But then you have to go back to where you were. Sure you could take note of the position but it would still be annoying.
Those points that are the hotspots of my current working are CTRL-F2-bookmarked anyway. And if I only want to know the type of a variable, Intellisense would open that little tooltip for me. I all boils down to being simply personal style, I guess.
Failure is not an option - it's built right in.
-
Wrong! Unless you are talking about how hard you hit the keys on your keyboard.
INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
Errm - I'm not sure if you are being subtly ironic here, or you missed the joke icon on my post. I'll give you the benefit of the doubt and go with subtly ironic.
Deja View - the feeling that you've seen this post before.
-
What are you talking about? If you are talking about variable type checking in C++, then you are wrong. I wish C was as tight with its type checking. Then again I wish C would allow me to declare a variable where ever I wanted too, instead of forcing me to create a new scope. P.S. I liked C, but I love C++.
INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
Actualy it arose from some code i wrote in .Net. I wrapped a generic HttpSession collection in something that exposed typed properties for each of the items it contained, And was told it was a total waste of my time. T
------------------------------- Carrier Bags - 21st Century Tumbleweed.
-
Actualy it arose from some code i wrote in .Net. I wrapped a generic HttpSession collection in something that exposed typed properties for each of the items it contained, And was told it was a total waste of my time. T
------------------------------- Carrier Bags - 21st Century Tumbleweed.
Tristan Rhodes wrote:
And was told it was a total waste of my time.
Why?
CleaKO
"I think you'll be okay here, they have a thin candy shell. 'Surprised you didn't know that.'" - Tommy (Tommy Boy)
"Fill it up again! Fill it up again! Once it hits your lips, it's so good!" - Frank the Tank (Old School) -
Tristan Rhodes wrote:
And was told it was a total waste of my time.
Why?
CleaKO
"I think you'll be okay here, they have a thin candy shell. 'Surprised you didn't know that.'" - Tommy (Tommy Boy)
"Fill it up again! Fill it up again! Once it hits your lips, it's so good!" - Frank the Tank (Old School)Because the general concencus was that "It's the most pointless piece of code" they had ever seen. :S
------------------------------- Carrier Bags - 21st Century Tumbleweed.
-
Because the general concencus was that "It's the most pointless piece of code" they had ever seen. :S
------------------------------- Carrier Bags - 21st Century Tumbleweed.
I'd have to see the code.
-
John R. Shaw wrote:
Then again I wish C would allow me to declare a variable where ever I wanted
I prefer to have all the declarations in one place (the top) so in C# I still do that by choice. But requiring such isn't very friendly, flexibility is good.
ewwww! Declare the variables as close to their first use as possible. I have spoken.
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
Because the general concencus was that "It's the most pointless piece of code" they had ever seen. :S
------------------------------- Carrier Bags - 21st Century Tumbleweed.
Maybe it was just the code. Strong typing is a good way to control up front what type of information you are looking for rather than waiting for it to hit the database or a flat file and finding out later it isnt what it should be.
CleaKO
"I think you'll be okay here, they have a thin candy shell. 'Surprised you didn't know that.'" - Tommy (Tommy Boy)
"Fill it up again! Fill it up again! Once it hits your lips, it's so good!" - Frank the Tank (Old School) -
I'd have to see the code.
public class SessionWrapper { private HttpSessionState session; // Constants public SessionWrapper() { session = HttpContext.Current.Session; } public string UserName { get{return (string)session[SE_USER_NAME];} set{session[SE_USER_NAME] = value;} } public int? LastPurchase { get{return (int?)session[SE_LAST_PURCHASE];} set{session[SE_LAST_PURCHASE] = value;} } // Etc }I'm actualy working on a code generator to build stuff like that for me, but at the time it was written manualy. My argument was its a strongly typed wrapper that exposes other developers to exactly what they need, what type it is, and hides the constants. T------------------------------- Carrier Bags - 21st Century Tumbleweed.
-
public class SessionWrapper { private HttpSessionState session; // Constants public SessionWrapper() { session = HttpContext.Current.Session; } public string UserName { get{return (string)session[SE_USER_NAME];} set{session[SE_USER_NAME] = value;} } public int? LastPurchase { get{return (int?)session[SE_LAST_PURCHASE];} set{session[SE_LAST_PURCHASE] = value;} } // Etc }I'm actualy working on a code generator to build stuff like that for me, but at the time it was written manualy. My argument was its a strongly typed wrapper that exposes other developers to exactly what they need, what type it is, and hides the constants. T------------------------------- Carrier Bags - 21st Century Tumbleweed.
Makes sense to me. A similar thing I do is with
ExecuteScalar(), which returnsobjectwhich then (usually) requires a test for null and a cast, and setting a default value if null. I wrote a wrapper likepublic virtual T ExecuteScalar<T>(T IfNull){...}to handle the cast. Any time I'm writing a scalar query and don't have to test for null and/or do a cast I save time, the code is more readable too. Usually, spending the time to encapsulate such common tasks will pay off. "A stitch in time saves nine." -
Makes sense to me. A similar thing I do is with
ExecuteScalar(), which returnsobjectwhich then (usually) requires a test for null and a cast, and setting a default value if null. I wrote a wrapper likepublic virtual T ExecuteScalar<T>(T IfNull){...}to handle the cast. Any time I'm writing a scalar query and don't have to test for null and/or do a cast I save time, the code is more readable too. Usually, spending the time to encapsulate such common tasks will pay off. "A stitch in time saves nine."Well i spent a few months crusading for sensible coding practices, and now i've given up. The other day i was told to remove it, re-centralise all the constants and simply use Session[AppConstants.CONST_NAME] to access everything.
------------------------------- Carrier Bags - 21st Century Tumbleweed.
-
Well i spent a few months crusading for sensible coding practices, and now i've given up. The other day i was told to remove it, re-centralise all the constants and simply use Session[AppConstants.CONST_NAME] to access everything.
------------------------------- Carrier Bags - 21st Century Tumbleweed.
Glad I'm in a small IT department and have free reign on what I write.
-
Glad I'm in a small IT department and have free reign on what I write.
I'm in a small IT department too, that was the CTO and Senior Developer pulling rank on my design decision. :S (I'm leaving in a week anyway :D ) T
------------------------------- Carrier Bags - 21st Century Tumbleweed.
-
Those points that are the hotspots of my current working are CTRL-F2-bookmarked anyway. And if I only want to know the type of a variable, Intellisense would open that little tooltip for me. I all boils down to being simply personal style, I guess.
Failure is not an option - it's built right in.
-
public class SessionWrapper { private HttpSessionState session; // Constants public SessionWrapper() { session = HttpContext.Current.Session; } public string UserName { get{return (string)session[SE_USER_NAME];} set{session[SE_USER_NAME] = value;} } public int? LastPurchase { get{return (int?)session[SE_LAST_PURCHASE];} set{session[SE_LAST_PURCHASE] = value;} } // Etc }I'm actualy working on a code generator to build stuff like that for me, but at the time it was written manualy. My argument was its a strongly typed wrapper that exposes other developers to exactly what they need, what type it is, and hides the constants. T------------------------------- Carrier Bags - 21st Century Tumbleweed.
I just spent the day (working from home) writing a wrapper for NumericUpDown that is generic and will take any of the built-in numerics, hide the actual decimal, and handle the casting so I don't have to. Ugly as Hillary, but it works.