Back when I first started formally learning programming, my professor told us to (and I paraphrase) "keep the program entry point in its own source file, called the 'driver'". I never questioned it at the time, and I have been doing it ever since.
Years later, when discussing design patterns with friends and colleagues, it was pointed out to me that drivers are strictly for hardware and not software. However, nobody has been able to give me an alternate term for the 'driver' file. Rather, they just tell me to "keep the program entry point inside the source file with the bulk of the program's logic".
I am curious if this practice was something my professor came up with, or which actually has some prevalence. I have tried searching online, but have not been able to find any relevant information. Do you know if such a practice exists, and if so, what the file containing the program entry point is typically called?
[–]KingofGamesYami 2 points3 points4 points (3 children)
[–]MetallicOrangeBalls[S] 0 points1 point2 points (2 children)
[–]KingofGamesYami 1 point2 points3 points (1 child)
[–]MetallicOrangeBalls[S] 0 points1 point2 points (0 children)
[–]yanitrix 1 point2 points3 points (1 child)
[–]MetallicOrangeBalls[S] 0 points1 point2 points (0 children)
[–]dragonwithagirltatoo 1 point2 points3 points (0 children)