A library of helper classes for simplifying every-day tasks in PHP. Classic.php classes are great for use in virtually any project. These classes are primarily intended to reduce the need to code and recode the same every-day algorithms in various projects. Each class is relatively independent, so you can include only those you need, and not the ones you don't. By focusing on every-day tasks, this collection remains simple to pick up and start using, while remaining relevant to the task at hand.
Classes found in Classic.php include:
- Database Access (Reading/Writing Data, and Managing the Database Itself)
- MySQLPDO (classic_php/databases/mysql_pdo.php) -- The super database class. Allows you to access the database using predefined PHP methods. In most cases you should instantiate one or more of the subclasses instead of this one.
- MySQLPDO_Read (classic_php/databases/mysql_pdo_read.php) -- Query the database using a SELECT statement.
- MySQLPDO_Write (classic_php/databases/mysql_pdo_write.php) -- Write data to the database using INSERT INTO, UPDATE, and DELETE statements.
- MySQLPDO_Manage (classic_php/databases/mysql_pdo_manage.php) -- Manage the database using CREATE TABLE, ALTER TABLE, and DROP TABLE statements.
- Data-Type Specific Classes
- ArrayProcessing (classic_php/data_types/array_processing.php) -- Adds additional functionality to help process arrays.
- Miscellaneous Helper Classes
- ErrorHandling (classic_php/misc/error_handling) -- Adds additional error handling methods to help handle errors and throw errors in code.
- Test (classic_php/misc/error_handling) -- Adds additional debug methods to help debug code.
- PHP >= 7.4 (Suggested: PHP >= 8.0)
This project currently uses versioned namespaces in order to distinguish between different versions of the library being run at the same time in the same PHP environment. This is especially helpful for WordPress plugins. For example, two WordPress plugins may use different versions of Classic.php on the same website. Using versioned namespaces prevents namespace collisions and race conditions (where one version may be used or the other, but not both, although both plugins assume their version is the one being used). In order to use this convention and still keep up with the PHP standards (PSR-4), we put all of the library code within a folder under the same name as the sub-namespace. Therefore when transitioning from one version of the library to the next, it is necessary to update the name of the folder where all of the code is found, and also to do a recursive search and replace to update all of the namespace declarations throughout the code.
Please note that while the version number is found in the namespace and the project folder, no version of the library project should contain past versions in separate folders. The version is only meant to distinguish between different versions of the library, not to include copies of any past versions in the library.
If you have any suggestions for new functionality which could reduce code duplication across many different kinds of projects, please create a new issue.