Reactor Engineers

[eluser]Basketcasesoftware[/eluser]
Probably true, Rick. But for me it's an exercise to better familiarize myself with the existing code base "under the hood". It's also a "proof of concept" issue. Right now I'm just working with one method in the entire class and trying to do so in a manner that doesn't break any legacy code.

How would you suggest eliminating the class? Right now one of the features of CI is "lazy loading". Nothing is loaded unless it is absolutely essential and even then it is loaded under programmer direction. The loader class seems to all the fulfillment of that objective. Maybe just creating an instance of each class in much the same way as the DataMapper system does its model class might be reasonable but that would break a lot of code. Already people complain about the problems with the switch from 1.7 to 2.0 CI.

You notice I didn't bitch about how things are done, I went and tried actually doing something constructive in an open, accountable manner. I have 30+ years in IT. I have nearly about 36 years in electronics. I have about 25 years in advanced calculus and statistics. And that's just a start. This is all good, but it isn't worth a spit unless I apply it constructively.