Hands on how to: add a section about pros and cons on separating or not declarations and definitions
1 unresolved thread
Merge request reports
Activity
added Fast MR label
assigned to @sgilles
99 99 ] 100 100 }, 101 { 102 "cell_type": "markdown", 103 "metadata": {}, 104 "source": [ 105 "## Declaration and definition" 106 ] 107 }, 108 { 109 "cell_type": "markdown", 110 "metadata": {}, 111 "source": [ 112 "We saw briefly [here](http://localhost:8888/lab/tree/1-ProceduralProgramming/4-Functions.ipynb#Function-declaration) and [there](http://localhost:8888/lab/tree/1-ProceduralProgramming/4-Functions.ipynb#Function-definition) what is the difference between the declaration and the definition of a function (and also from other stuff such as objects that we'll see in part 3).\n", 113 "\n", 114 "We'll explain in a [late notebook](http://localhost:8888/lab/tree/6-InRealEnvironment/2-FileStructure.ipynb) how to properly structure a project with several files, but for the hands-on the idea is not to bother with this and each exercise is fully present in one file (see above).\n", Was not a typo but you're right clunky english... However on this one @vrouvrea was not in agreement (See Mattermost discussion)
I suggest we drop it? MR !100 (merged) covers it better to my mind
Please register or sign in to reply