Timeline for Default values - are they good or evil?
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 19, 2023 at 17:45 | comment | added | Juan Perez | Instead of having default values, you could have a "default" function doStuff() that doesn't take arguments , and a "non-standard" function doStuffWeirdly(..weird args) that does. All the advantages of defaults without any of the disadvantages. | |
| Oct 15, 2011 at 13:25 | vote | accept | CommunityBot | ||
| Mar 31, 2011 at 14:38 | comment | added | Berin Loritsch | Right, and if most uses of an FTP service use new FtpService() the one that sets an alternate port will stand out (service.SetPort(12345)). | |
| Mar 31, 2011 at 14:12 | comment | added | Matthew Scharley | @Andrew if there's a dozen calls to Foo() and one call to Foo("bar"), that one call tends to stand out and is hence more visible. | |
| Mar 31, 2011 at 13:29 | comment | added | user18404 | Thanks for pointing me to "Convention over Configuration" concept. I did use it without knowing it has a name. Can you explain this rule: "Non-standard configurations are more visible when you use defaults." please. | |
| Mar 31, 2011 at 13:20 | vote | accept | CommunityBot | ||
| Mar 31, 2011 at 13:24 | |||||
| Mar 31, 2011 at 12:30 | history | edited | Berin Loritsch | CC BY-SA 2.5 | readability |
| Mar 31, 2011 at 12:22 | history | answered | Berin Loritsch | CC BY-SA 2.5 |