The most common issue for non-OOP is:
how to prevent conflict of function name when the project becomes extremely huge?
For OOP we can simply put the functions into different classes,but what's the approach for procedure programming?
+4
A:
In C++, without using OOP, you would use namespaces.
In C, people tend to create functions with prefixes (e.g. "sqlite3_some_function_name") and/or marking non-public functions static.
Anyway, when using long and descriptive names for functions, no two functions will have the same name OR if they do, they're identical and one of them can be removed.
AndiDog
2010-02-20 20:01:14
By marking non-public functions static,it's only visible within the very file,right?
2010-02-20 20:05:53
Yes, that's right.
AndiDog
2010-02-20 20:11:38
Did `c` support `namespace` by the time windows os comes out?
2010-02-20 20:15:12
The Windows API defines functions in C, not C++. Only C++ supports namespaces, C still doesn't. That's why I said that in C you'd usually use prefixed function names.
AndiDog
2010-02-20 20:21:42
So for c projects,the only approach is "prefixed function names"?
2010-02-20 20:27:49
Yes, it's the only bulletproof solution IMO.
AndiDog
2010-02-20 20:30:36