Quote:
Originally Posted by cdcox
Goto
I know, goto isn't the best coding practice. But it can sure come in handy for events that can happen at multiple places in the code, like touchdowns. I'm hoping that I can move a few things around to get rid of the goto statments.
To me, writing code is much easier than dealing with package installs and upgrades. I'm still running CI 1.7, so I'd have to do the upgrade to 2.0, which looks time consuming. Then get php 5.4 working on my localhost. Then hope that would take care of the error messages on the production site that are pointing to the CI core, not to my code. So even if I updated, it isn't clear that would take care the error messages that look very difficult to track down.
|
Yikes..
If it were me, I'd bite the bullet and move everything to php 5.4 and CI 2.1.1 .. since you will have to do so at some point anyway... BUT if you want to wait on that nightmare.. then getting rid of GOTO is a good idea anyway.
Can't you just make classes/functions that can be called instead?
Again, if you need a hand on anything I can whip through php/CI code pretty quickly and debug. I have also installed PHP 5.3+ and CI 2+ about a dozen times this year so feel free to ask me there as well.
Your production server an Amazon instance? or something similar?