Content deleted Content added
Line 79:
I agree that this article is poorly written and self-contradictory. It begins with a definition that's dubious at best, but goes on to provide a great definition of a monolithic program - any program where the smallest usable component is the program itself. I think as far I'm concerned Modular programming is amonolithic programming (i.e. any program that is not monolithic is modular by definition).
[[User:Djonesuk|Djonesuk]] ([[User talk:Djonesuk|talk]]) 16:26, 1 November 2010 (UTC)
I'd say #include and the systematic use of defines to avoid multiple including is a way to manually approach modularisation. It's the same as like using a struct with function pointers to emulate OOP. Not the same, not as safe, not as easy, but with C it is the best thing achievable. Moreover the way that e.g. a Pascal or Modula-2 "auto-make" a binary is impossible with C too. You always need to manually/externally keep an compilation order.
[[Special:Contributions/88.159.64.210|88.159.64.210]] ([[User talk:88.159.64.210|talk]]) 16:29, 18 December 2010 (UTC)
== Old stuff ==
| |||