Skip to main content
10 events
when toggle format what by license comment
Nov 2, 2023 at 11:45 history edited Doc Brown CC BY-SA 4.0
Broken link fixed
Aug 23, 2011 at 6:41 comment added jwenting @Secure maybe not in an in-house application, but if you're maintaining a public API like the Windows API, it's a major problem.
Aug 22, 2011 at 23:30 history made wiki Post Made Community Wiki by user unknown
Aug 22, 2011 at 17:14 comment added Joel @Secure: I would argue that's what automated tests should be doing. Not programmers.
Aug 22, 2011 at 13:56 comment added Secure A type change is a quite significant code modification. Isn't it a good thing to check all uses and occurrences of a type changed variable, if the statements and the calculations are still working as expected with the new type? Personally, I don't think this is a counter-argument to HN that it forces you to search and replace all occurrences, but YMMV.
Aug 22, 2011 at 5:43 comment added jwenting @David just look at the Win32 API which is riddled with variables, parameters, and even method names which using Hungarian notation (which is a requirement at MS) indicate an 8 bit or 16 bit value when in fact they've all been 32 bit values since the introduction of Windows 95 back in 1994 (so almost 17 years ago).
Aug 22, 2011 at 4:19 comment added Marty Pitt The linked article is fantastic, and highly worth a read. +1
Aug 22, 2011 at 0:41 comment added David Hammen "What happens when you change your int to a different type like long ..." Simple: <sarcasm> Don't change the name because there's no telling how many places the change will ripple.</sarcasm> So now you have a variable whose Hungarian name conflicts with its implementation. There is absolutely no way to tell how widespread the effects of changing the name will be if the variable/function has public visibility.
Aug 21, 2011 at 16:48 history edited user7519 CC BY-SA 3.0
added 105 characters in body
Aug 21, 2011 at 16:43 history answered user7519 CC BY-SA 3.0