User Guide: Libraries vs Core Classes

[eluser]wiredesignz[/eluser]
@oribani, There is a more appropriate place to post details of any spelling mistakes that you may have discovered in the User Guide.

As for helpers vs libraries, you are correct that any file containing one or more related functions or methods is termed a library. However for the sake of getting into the CodeIgniter frame of mind you are asked to consider the functionality of these libraries when describing them.

Controllers, Models and Views are pretty self explanatory.

CodeIgniter helpers are libraries of related procedural functions and they have global scope.

All CodeIgniter library files contain related object oriented methods and they are automatically instantiated by the core loader class and attached to the controller object for you.

Core libraries can be replaced by your own that bear the same file name but they must contain the "CI_" class prefix which makes them different to your user libraries.

Core libraries can be extended by your own that bear the subclass prefix of the core library file name and class name.

I don't believe you can replace and extend a core library at the same time. (untested)

Plugin's are also libraries which are loaded but are not instantiated by the framework, therefore they can be procedural or object oriented. (the single function in a plugin idea is not enforced.)

I'm not sure if this helps, but in any case understanding all of this is very much a CodeIgniter framework thing.