Timeline for Convention where to place unexportable functions
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 15, 2017 at 9:38 | vote | accept | Filip Bartuzi | ||
| Mar 10, 2017 at 16:58 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 8, 2017 at 16:16 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 9, 2017 at 15:37 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 16, 2016 at 16:30 | comment | added | Robert Harvey | There you go. That's as good a guideline as any. | |
| Nov 16, 2016 at 16:30 | comment | added | Filip Bartuzi | @RobertHarvey Many languages have policy to put private methods at the bottom of class definition. If you think about math.js file as a class than moving 'private' functions at the bottom makes sense | |
| Nov 16, 2016 at 15:21 | comment | added | Robert Harvey | This is a matter of taste, not policy. Put your private functions where they make most sense to you. | |
| Nov 16, 2016 at 12:42 | answer | added | Walfrat | timeline score: 0 | |
| Nov 16, 2016 at 12:35 | history | asked | Filip Bartuzi | CC BY-SA 3.0 |