X# Core - which way?
Posted: Mon Jul 02, 2018 5:54 pm
Hi Dick
Each to his own I guess.
> why do I have to manually change a namespace in multiple files including obscure files VS apparently needs to support it's solutions.
You don’t, and VS does not require it.
If you choose to write your program in one namespace in one file there is nothing to stop you. In that case using VS would probably be overkill.
So the question becomes what is the advantage of distributing source code over multiple files in this way?
My answer to that is: whenever trying to do something new, look a how nature does it (that will be the most efficient and streamlined) and do it the way we as human beings would do things naturally. Look at what we are good at and then capitalise on it.
I look at any program, when running, as being a 3D dynamic object.
Taking that view, a program has breadth and depth. We think this way naturally but not at the same time. By splitting code across files and namespaces we can arrange it, or rather match its structure to the way we think. As our program evolves during development things will change, names will not convey what the code is actually doing and so on. Thus we need re-factoring.
Hope that makes some sense.
Terry
Each to his own I guess.
> why do I have to manually change a namespace in multiple files including obscure files VS apparently needs to support it's solutions.
You don’t, and VS does not require it.
If you choose to write your program in one namespace in one file there is nothing to stop you. In that case using VS would probably be overkill.
So the question becomes what is the advantage of distributing source code over multiple files in this way?
My answer to that is: whenever trying to do something new, look a how nature does it (that will be the most efficient and streamlined) and do it the way we as human beings would do things naturally. Look at what we are good at and then capitalise on it.
I look at any program, when running, as being a 3D dynamic object.
Taking that view, a program has breadth and depth. We think this way naturally but not at the same time. By splitting code across files and namespaces we can arrange it, or rather match its structure to the way we think. As our program evolves during development things will change, names will not convey what the code is actually doing and so on. Thus we need re-factoring.
Hope that makes some sense.
Terry
