934451 wrote:It's a pretty common mistake, but it is a mistake.
... Initially we dint have the big picture. So we developed individual procedures and functons as we progressed with our development.
Now 6 months into this project, we realize, we need to logically group these procedures into packages.
Is this natural with all development projects, or did we make a mistake in not initially creating packages.
I am asking this question, as we see a lot of rework in grouping the procedures into packages.Sorry, I don't know of any easy way to fix the problem.
I do see it is not soo much of a re-work, I would re-phrase it as more of tweaking of code, both at the front-end and back-end.
Why would there be any rework to take a procedure named 'myProc' and put it into a package named 'myPack'? You now just use myPack.myProc to refer to it.