Survey Results

FirstPrevNext

Re: Formatting is important because.... UltraJoe30-Jul-02 7:55 UltraJoe 30-Jul-02 7:55  So does appPath, and you don't have to worry about changing it from char* to CString. Re: Formatting is important because.... Armen Hakobyan30-Jul-02 11:53 Armen Hakobyan 30-Jul-02 11:53  The name lpszAppPath makes clear its type and what methods to use without going to its definition. And how often do you change char* to CString ? #define __ARMEN_H__ Re: Formatting is important because.... UltraJoe31-Jul-02 8:04 UltraJoe 31-Jul-02 8:04  Armen Hakobyan wrote: The name lpszAppPath makes clear its type and what methods to use without going to its definition. IMHO, I'd rather go back to the definition (and be sure somebody didn't change the type without changing the name!) than to wade through the garbage just to find the purpose of the identifier. Armen Hakobyan wrote: And how often do you change char* to CString ? During prototyping, more often than one might think. Re: Formatting is important because.... Armen Hakobyan31-Jul-02 11:47 Armen Hakobyan 31-Jul-02 11:47  Ok ok. #define __ARMEN_H__ Re: Formatting is important because.... Philip Patrick31-Jul-02 1:56 Philip Patrick 31-Jul-02 1:56  appPath doesn't say nothing to me except that this is a path and suppose to be some sort of string, thought it doesn't have. We, for example, have paths defined in Database, so the path can be actually a long variable - ID in DB. See? Now I saw appPath and have NO idea what you mean by that, I have to go and search where it was defined, and if you hate HN, you won't use "m_" declaration for class members also, so your variable can be define anywhere. This increases programming time of your product for example. BUT if you had declared your variable lpszAppPath, I can be sure that this is a string (LPCTSTR), or if you declared nAppPath (in our particular case) I know that this is an ID to path in Database. Simple as is Philip Patrick Web-site: www.stpworks.com "Two beer or not two beer?" Shakesbeer Re: Formatting is important because.... UltraJoe31-Jul-02 8:09 UltraJoe 31-Jul-02 8:09  appPath tells me that it's the path to some sort of application; the details would depend on context. However, that gives me significantly more useful information than, say, lpszText, which tells me the datatype, but not how the stupid thing is used. HN requires the developers to keep all occurrences of the identifier consistent with its datatype. I'd much rather go back to its definition, where I can see in detail what the compiler thinks it's supposed to be, than risk making a bad assumption. But we've gone way off topic here. Re: Formatting is important because.... Philip Patrick31-Jul-02 9:36 Philip Patrick 31-Jul-02 9:36  Well, noone talking about lpszText, but about lpszAppPath, which tells you type AND what this variable for. UltraJoe wrote: I'd much rather go back to its definition, I suppose that you mean a small project, maybe 1-2 classes/cpp files in it. But think about something bigger. Example is not very far - in my company, there are like 30 different modules (.dll and .exe) written by different people. And you use someone else's module and you have no idea in it, you just use it. So to know the type you should find where the variable is declared. It can be global, it can be member of class or just local to the function. Using your method, you can't do that without searching for definition, which can take a lot of time, or maybe you should go to that programmer who did the module and ask him? I would fire you for disturbing people by asking such questions lol, or maybe that programmer who has no idea in HN, depends on situation. I tested that on my own skin, we had some people who liked to call their variables like database_connection. Yeah it says what is that, but what type? ADO Connection object? MFC connection? Just a connection string? And is this a pointer? Philip Patrick Web-site: www.stpworks.com "Two beer or not two beer?" Shakesbeer Re: Formatting is important because.... UltraJoe1-Aug-02 10:01 UltraJoe 1-Aug-02 10:01  Philip Patrick wrote: Well, noone talking about lpszText, but about lpszAppPath, which tells you type AND what this variable for. Okay, I'm probably not playing fair by changing examples in mid-stream; I should've used lpszText from the start. Still, I'd much rather search for the definition (more on that in a second) than trip over the semantics of a line of code by trudging through all the Hungarian junque. For me, the understandability of the code decreases exponentially as I see more "lpsz" garbage. Numerous people have noted that searching for a definition can be tedious. I disagree; it won't be tedious IF the project is organized well, not just in terms of classes or a single file, but also in terms of what goes into what files. An undecorated name is either an argument to the current function/method, in the class or a superclass thereof, or a global . (No, I'm not trying to claim that globals are good, nor am I condemning them. Completely different subject.) That makes 3 places to look, and that's it. More often than not, I'll need that file anyhow, for comments relating to the variable (when necessary), or other information that won't come from Hungarian Notation anyhow. Re: Formatting is important because.... KarstenK30-Jul-02 1:10 KarstenK 30-Jul-02 1:10  Totally right, the format enhances transparency. Only well formatted and commentented code enables to work other programmers than the original coder on the source. AND: in well formatted code experienced programmers see the quality or bugs at first side. Re: Formatting is important because.... Marc Clifton31-Jul-02 11:51 Marc Clifton 31-Jul-02 11:51  All code must go through a development/debug/maintenance cycle. Right. In the land of Oz. I've preached that to various companies (like Robot Research, eventually bought by Sensormatic), or like Integration Partners, when I worked for them. Management barely understand why a debug cycle is necessary ("can't you just program it without bugs???") and I've never been able to convince any manager that a product needs to be funded for the maintenance cycle, let alone a phase-out cycle. I'm sick of it all, which is why I'm a consultant now. And I'm sick of it enough that I'm naming the bozo places I used to work for, otherwise, there will never be accountability. As far as style goes, other than getting the naming convention right, it's cheaper to buy a code formatter than to get two people, let alone 10 or 20, to agree on style. Marc If it looks bad, it most likely runs bad as well... George28-Jul-02 21:00 George 28-Jul-02 21:00  Poor programmers usually suck at both code formatting and code performance. If you see a bad looking code you can be sure it will give you a headache. Re: If it looks bad, it most likely runs bad as well... Alexandru Savescu28-Jul-02 23:21 Alexandru Savescu 28-Jul-02 23:21  George wrote: Poor programmers usually suck at both code formatting and code performance. It depends! I like to indent a la MS-stlye, I use a lot of blank lines to separate program functionality etc. I hate Java-formatting style However I have collegues that do not use blank lines, use Java-indentation etc. But, their code is good, just does not look nice to me. Best regards, Alexandru Savescu Re: If it looks bad, it most likely runs bad as well... George29-Jul-02 3:26 George 29-Jul-02 3:26  Alexpro wrote: It depends! Of course! Alexpro wrote: However I have collegues that do not use blank lines, use Java-indentation etc. But, their code is good, just does not look nice to me. Well, I am not talking about Java-style vs MS-Style. I am rather talking about having and not having a style. Some people really can make a code look unreadable, because they don't format it at all. Re: If it looks bad, it most likely runs bad as well... Anonymous29-Jul-02 22:32 Anonymous 29-Jul-02 22:32  bla bla bla whaterver dude bla bla bla Re: If it looks bad, it most likely runs bad as well... Tim Smith31-Jul-02 5:13 Tim Smith 31-Jul-02 5:13  I guess you are a spew coder then? Tim Smith "Programmers are always surrounded by complexity; we can not avoid it... If our basic tool, the language in which we design and code our programs, is also complicated, the language itself becomes part of the problem rather that part of the solution." Hoare - 1980 ACM Turing Award Lecture Re: If it looks bad, it most likely runs bad as well... Mike Pulice30-Jul-02 12:06 Mike Pulice 30-Jul-02 12:06  I agree with that statement. I think its a matter of pride. I want it to look good and work good. If my seniors and principles look at my code or go through a code review and it looks like garbage and confusing then i did not do my job! My job is to write clear and concise code that works according to spec. mike Mike "Badvox" Re: If it looks bad, it most likely runs bad as well... SHaroz1-Aug-02 12:42 SHaroz 1-Aug-02 12:42  You obviously have never programmed in assembly where all code looks like meeningless sh*t Re: If it looks bad, it most likely runs bad as well... jan larsen2-Aug-02 2:12 jan larsen 2-Aug-02 2:12  It does?   When doing assembler you just have to be even MORE carefull about formatting and clarifications, otherwise you will most likely end up with a thousand lines of unusable garbage. I have seen asm code that was just one step from C, and other code that was a pile of s**t, mnemonics and numbers. "After all it's just text at the end of the day. - Colin Davies Re: If it looks bad, it most likely runs bad as well... Paul Watson2-Aug-02 6:20 Paul Watson 2-Aug-02 6:20  George wrote: Poor programmers usually suck at both code formatting and code performance. I could out indent and out format you into the next solar system. Why? From my HTML work I have learnt to format like the devil. It means a lot in HTML. But no way in hell I could out programme you in C++. regards, Paul Watson Bluegrass Cape Town, South Africa The greatest thing you'll ever learn is just to love, and to be loved in return - Moulin Rouge Alison Pentland wrote: I now have an image of you in front of the mirror in the morning, wearing your knickers, socks and shoes trying to decided if they match! I am a zealot Christian Graus28-Jul-02 19:51 Christian Graus 28-Jul-02 19:51  I am a zealot for coding standards, but no-one in their right mind can say that formatting is equally important to performance, I mean, which does the user *see* ? Christian come on all you MS suckups, defend your sugar-daddy now. - Chris Losinger - 11/07/2002 Re: I am a zealot James T. Johnson28-Jul-02 20:06 James T. Johnson 28-Jul-02 20:06  That depends on what you are looking at. If you are looking at the here and now then by all means current performance means everything. But if you look at the lifetime of an application the extra time it takes to maintain the poorly formatted code could add a lot more time than the few extra cycles you save by using a particular way of doing things. Personally I go for readability, as you could tell from my stance on casting etc Then again 90% of what I have written are database applications where communicating with the server takes far longer than saving a few cycles will be worth. James "Java is free - and worth every penny." - Christian Graus Re: I am a zealot Christian Graus28-Jul-02 20:19 Christian Graus 28-Jul-02 20:19  James T. Johnson wrote: But if you look at the lifetime of an application the extra time it takes to maintain the poorly formatted code could add a lot more time than the few extra cycles you save by using a particular way of doing things. I think you missed my point. James T. Johnson wrote: If you are looking at the here and now then by all means current performance means everything. Current performance IS everything. But to be honest, what I was trying to say is that I do not see the dichotomy, but if I had to choose, performance is the winner. James T. Johnson wrote: Personally I go for readability, as you could tell from my stance on casting etc I hope you're being ironic.... A major reason I hate all that casting is that C# is hard to read at times because it's too verbose. Overall my point ( obviously poorly made ) is that there is no dichotomy but if a false one is to be imposed by the poll, then performance is obviously number one, although I think performance is likely to *improve* if the code is well formatted, because it's easier for people to go back and change other peoples code to make improvements if it is easy to read. Christian come on all you MS suckups, defend your sugar-daddy now. - Chris Losinger - 11/07/2002 Re: I am a zealot James T. Johnson28-Jul-02 21:12 James T. Johnson 28-Jul-02 21:12  Christian Graus wrote: I think you missed my point. Probably Christian Graus wrote: I hope you're being ironic.... A major reason I hate all that casting is that C# is hard to read at times because it's too verbose. I don't find it that hard to read; but it depends on how you are doing it. If I have to cast, I prefer to store the result in a variable so I don't have to cast again. I also prefer to have only one or two member access per line. Not my style ((BarRow) ((Foo) fooCollection[4]).Rows[3]).Baz(); My style Foo foo = (Foo) fooCollection[4];<br /> BarRow barRow = (BarRow) foo.Rows[3];<br /> <br /> barRow.Baz(); Which I think is the kind of formatting vs performance that the survey was asking about. Here a few cycles are wasted because it stores the results of each line in a variable; only to be used once. I would think that a good optimizing compiler would see that this is the case so it would compile down to the better version; but I've seen weird bugs with the VC6 optimizer (a simple 'center in window' type function was messed up). James "Java is free - and worth every penny." - Christian Graus Re: I am a zealot Tomasz Sowinski29-Jul-02 1:11 Tomasz Sowinski 29-Jul-02 1:11  Christian Graus wrote: Current performance IS everything Well, let's see. If you have function refreshing the window which takes 1e-6 seconds, how much time (max) would you like to spent to improve the performance 10 times? Tomasz Sowinski -- http://www.shooltz.com - It's for protection - Protection from what? Zee Germans? Re: I am a zealot Christian Graus29-Jul-02 1:40 Christian Graus 29-Jul-02 1:40  Tomasz Sowinski wrote: Well, let's see. If you have function refreshing the window which takes 1e-6 seconds, how much time (max) would you like to spent to improve the performance 10 times? It doesn't matter what I say, does it ? As I said before, in the false dichotomy between pretty code and performance, performance is more important. That does not mean we need to keep optimising when performance is perfectly acceptable. Christian come on all you MS suckups, defend your sugar-daddy now. - Chris Losinger - 11/07/2002

Last Visit: 31-Dec-99 18:00     Last Update: 29-Apr-24 4:15 Refresh ᐊ Prev1234 Next ᐅ

General    News    Suggestion    Question    Bug    Answer    Joke    Praise    Rant    Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.