Survey Results

FirstPrev Next

Re: how about &quot;as short as possible&quot; ? stephen.hazel31-Jan-05 6:39 stephen.hazel 31-Jan-05 6:39  uhhh, that's short, but not consistently named... whatever... whenever I have to pick up someone else's code, I totally reformat it into my preferred conventions. Much easier to check for errors that way. And well worth the time i spend doing it. But if the code belongs to someone else, I leave it ugly. (Or convert it to my format to understand it and make the changes in "ugly format") When you get right down to it, the format you use is the format that works best for you. I'm picky. You'll find my code rather terse and extremely neat. I don't particularly care how others write their code... Whatever works... It's a religious thing. Not gonna try to force my beliefs on others... ...Steve Re: how about &quot;as short as possible&quot; ? Nitron31-Jan-05 8:06 Nitron 31-Jan-05 8:06  I was just giving you a hard time, Steve. Did you not see the: at the end... ~Nitron. ññòòïðïðB A start Re: how about &quot;as short as possible&quot; ? stephen.hazel31-Jan-05 8:47 stephen.hazel 31-Jan-05 8:47  sorry - it's been one of thooooose monday mornings... Re: how about &quot;as short as possible&quot; ? toxcct1-Feb-05 6:18 toxcct 1-Feb-05 6:18  can't the while loop brackets ({ }) thrown off ?? TOXCCT >>> GEII power [toxcct][VisualCalc] Kind of a hard question hannahb31-Jan-05 3:34 hannahb 31-Jan-05 3:34  C# - camel case straight C - this_is_my_var C++ - hugarian m_bChecked So yeah, I don't really know what to vote for.... Brad Depends on the library default ed welch31-Jan-05 2:01 ed welch 31-Jan-05 2:01  When you weigh up the pros and cons there is no one style better than the other, so better to use the same style as the existing codebase, otherwise you end up with a mish-mash of mixed styles in your code. Re: Depends on the library default Nemanja Trifunovic1-Feb-05 4:31 Nemanja Trifunovic 1-Feb-05 4:31  ed welch wrote: there is no one style better than the other Amen to that!!! Finally, a voice of reason. My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it. Pascal with humps Gary R. Wheeler31-Jan-05 0:46 Gary R. Wheeler 31-Jan-05 0:46  Ours is a mix of Pascal (publics and protected), camel case (private), C-style (locals within a method), and FORTRAN (#define's). I suppose the fact that we 'encode' access and visibility in our names does mean we use Hungarian notation (the notion that you encode metadata about the value in the name). Software Zen: delete this; Mix of Hungarian and Camel Caps Antti Keskinen31-Jan-05 0:01 Antti Keskinen 31-Jan-05 0:01  I use somewhat of a mix of Hungarian notation and Camel Caps. For example, all object and reference variables start with a prefix obj or ref. Pointers are p. Global variables have a prefix g_. For standard variables, 'n' is integer, 's' is short, 'c' is char, 'l' is long, 'f' is float and 'd' is double. For pointer-to-value types, only the pointer prefix is used, aka the type of pointed-to is not visible in the declaration. I've fathomed a small syntax for my variables expr: [g_][type][name in Camel Caps] The problem is that if I have a type double, like in g_dMaxSum, and I need to change it to float, it's always a find & replace run. I use this for all languages I use. It might be difficult to read, and problematic in change situations, but I like it -Antti Keskinen ---------------------------------------------- "If we wrote a report stating we saw a jet fighter with a howitzer, who's going to believe us ?" -- R.A.F. pilot quote on seeing a Me 262 armed with a 50mm Mauser cannon. I indicate scope in prefix Bamaco230-Jan-05 23:46 Bamaco2 30-Jan-05 23:46  This way, looking at code, I can't tell the type of a thing, but I can tell what scope it has. prefix meaning "a" attributes "g" static or global "k" constant "p" parameter ex: extern const COLORREF kDefaultColor; struct TPixel { COLORREF aBackColor; CPoint aPosition; void color( COLORREF pColor = kDefaultColor); COLORREF color() const; }; Furthermore, I use "C" or "T" to denote a C++ TYPE or a C STRUCT. On member function accessors, I use "camelCase". On member function not use for accessors, I use "PascalCase". On local (stack) variable, I use "c_style_case". I think that encoding the TYPE of something in a variable name defeats the purpose of a language with strong type checking emphasis, such as C++. I find it easyer to encode the scope. At least, it makes it easy to read. Assuming local variables... Colin Angus Mackay30-Jan-05 22:58 Colin Angus Mackay 30-Jan-05 22:58  Then camel case. Do you want to know more? WDevs.com - Open Source Code Hosting, Blogs, FTP, Mail and Forums Depends on the language Michael P Butler30-Jan-05 21:56 Michael P Butler 30-Jan-05 21:56  My C++ code still uses Hungarian but my C# code follows the new guidelines and so is mainly camelCase for variables and PascalCase for methods. Michael CP Blog [^] Development Blog [^] Re: Depends on the language Brian Delahunty30-Jan-05 22:21 Brian Delahunty 30-Jan-05 22:21  Same here. But with C# I still have a small piece of Hungarian in that I use m_ for object level variables. Regards, Brian Dela Now Bloging![^] Re: Depends on the language Gary R. Wheeler31-Jan-05 0:48 Gary R. Wheeler 31-Jan-05 0:48  Brian Delahunty wrote: I use m_ for object level variables I still use the "m_" prefix for variables in a dialog box that are subject to dialog data exchange. Old habits die hard, I suppose. Software Zen: delete this; as always... CListCtrl Aqualic30-Jan-05 20:49 Aqualic 30-Jan-05 20:49  i assume this refer to Hungarian notation with prefixes. Re: as always... CListCtrl Uwe Keim2-Feb-05 23:27 Uwe Keim 2-Feb-05 23:27  In fact, this time, CListCtrl is not that off-topic and therefore should be avoided for this survey. -- Affordable Windows-based CMS: www.zeta-producer.com A bit of an alteration... Ray Cassick30-Jan-05 18:39 Ray Cassick 30-Jan-05 18:39  I do use prefixes sometimes but only in a few cases: 1) A leading 'm' to show module level vars 2) A prefix to show referances to controls (ie: frm, cmd, cmb, etc...) Paul Watson wrote: "At the end of the day it is what you produce that counts, not how many doctorates you have on the wall." George Carlin wrote: "Don't sweat the petty things, and don't pet the sweaty things." Jörgen Sigvardsson wrote: If the physicists find a universal theory describing the laws of universe, I'm sure the a**hole constant will be an integral part of that theory. Some time i create my Own ThatsAlok30-Jan-05 21:47 ThatsAlok 30-Jan-05 21:47  like i Created prefix l_ for local member of function "I Think this Will Help" <h5  alok gupta="" <br=""> visit me at http://www.thisisalok.tk Re: Some time i create my Own Blake Miller31-Jan-05 7:45 Blake Miller 31-Jan-05 7:45  I also put s_ in front of variables declared 'static' at file scope. I put S_ in front of functions declared static at file scope. Re: Some time i create my Own feline_dracoform31-Jan-05 23:42 feline_dracoform 31-Jan-05 23:42  i like this idea i think i will adopt this for static variables. i find it very important to know which ones are static when i find i have to use one, but i never had a consistent way of indicating them. zen is the art of being at one with the two'ness Re: Some time i create my Own James R. Twine2-Feb-05 6:09 James R. Twine 2-Feb-05 6:09     Same thing for using g_ for global objects.  Also:      ms_ for member static variables.      gs_ for global static variables.    I also do the S_ for static member methods/functions.    Peace! -=- James If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong! Tip for new SUV drivers: Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road! DeleteFXPFiles & CheckFavorites

Last Visit: 31-Dec-99 18:00     Last Update: 29-Apr-24 8:48 Refresh ᐊ Prev1234

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.