Manual includes vs autoloading in PHP - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to manually include the file 'User.php'.

PHP

<?php
[1] 'User.php';
$user = new User();
?>

Drag options to blanks, or click blank then click option'

Aload

Binclude

Crequire_once

Dautoload

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'autoload' which is not a PHP statement for manual includes.

Using 'load' which is not a valid PHP keyword.

The include statement is used to manually include a PHP file.

2fill in blank

medium

Complete the code to register an autoloader function named 'myAutoloader'.

PHP

<?php
spl_autoload_[1]('myAutoloader');
?>

Drag options to blanks, or click blank then click option'

Aregister

Binclude

Cautoload

Dload

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'include' or 'load' which are not functions to register autoloaders.

Using 'spl_register' which is not a valid PHP function.

The function spl_register does not exist, but spl_autoload_register does. The correct function is spl_autoload_register.

3fill in blank

hard

Fix the error in the autoloader function to correctly load class files from the 'classes/' directory.

PHP

<?php
function myAutoloader($className) {
    include_once 'classes/' . [1] . '.php';
}
spl_autoload_register('myAutoloader');
?>

Drag options to blanks, or click blank then click option'

A$class_name

B$classname

CclassName

D$className

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different variable name than the function parameter.

Forgetting the dollar sign ($) before the variable.

The parameter name is $className, so it must be used exactly as is inside the function.

4fill in blank

hard

Fill both blanks to create an autoloader that loads classes from the 'lib/' directory and uses the class name with '.class.php' extension.

PHP

<?php
function [1]($class) {
    include_once 'lib/' . $class . [2];
}
spl_autoload_register('[1]');

Drag options to blanks, or click blank then click option'

AmyAutoloader

B.php

C.class.php

Dautoload

Attempts:

3 left

💡 Hint

Common Mistakes

Using '.php' instead of '.class.php' for the file extension.

Using a different function name than the one registered.

The function name is 'myAutoloader' and the file extension is '.class.php' to match the class files.

5fill in blank

hard

Fill all three blanks to create an autoloader that loads classes from the 'src/' directory, converts class names to lowercase, and uses '.inc.php' extension.

PHP

<?php
function [1]($className) {
    $file = 'src/' . strtolower([2]) . [3];
    if (file_exists($file)) {
        include_once $file;
    }
}
spl_autoload_register('[1]');

Drag options to blanks, or click blank then click option'

AautoLoadClass

B$className

C'.inc.php'

Dstrtolower

Attempts:

3 left

💡 Hint

Common Mistakes

Using the variable without the dollar sign.

Using wrong file extension or function name.

The function name is 'autoLoadClass', the variable is '$className', and the file extension is '.inc.php'.

Practice

1. What is the main difference between manual includes and autoloading in PHP?

easy

A. Manual includes require you to write code to load each file, autoloading loads classes automatically.

B. Manual includes load classes automatically, autoloading requires manual file loading.

C. Manual includes are faster than autoloading in all cases.

D. Autoloading requires you to write code to include files manually.

Solution

1. Step 1: Understand manual includes

   Manual includes require explicit code like include or require to load files.

2. Step 2: Understand autoloading

   Autoloading automatically loads class files when you create an object, without explicit includes.

3. Final Answer:

   Manual includes require you to write code to load each file, autoloading loads classes automatically. -> Option A

4. Quick Check:

   Manual includes = explicit code, Autoloading = automatic loading [OK]

Hint: Manual includes need explicit code; autoloading is automatic [OK]

Common Mistakes:

• Thinking autoloading needs manual include statements
• Believing manual includes load classes automatically
• Confusing speed differences between the two

2. Which of the following is the correct syntax to register an autoloader function in PHP?

easy

A. autoload_register('myLoader');

B. spl_autoload_register('myLoader');

C. register_autoload('myLoader');

D. spl_register_autoload('myLoader');

Solution

1. Step 1: Recall PHP autoload function

   PHP uses spl_autoload_register to register autoload functions.

2. Step 2: Check syntax correctness

   The correct function call is spl_autoload_register('myLoader'); where 'myLoader' is your function name.

3. Final Answer:

   spl_autoload_register('myLoader'); -> Option B

4. Quick Check:

   Correct autoload function = spl_autoload_register [OK]

Hint: Use spl_autoload_register to set autoload functions [OK]

Common Mistakes:

• Using wrong function names like register_autoload
• Mixing up function order or spelling
• Forgetting to pass the function name as a string

3. Given the following code, what will be the output?

<?php
spl_autoload_register(function ($class) {
    include $class . '.php';
});

$obj = new Car();
echo $obj->drive();
?>

Assuming Car.php exists and defines class Car with method drive() returning "Driving".

medium

A. Driving

B. Parse error

C. Nothing is printed

D. Fatal error: Class 'Car' not found

Solution

1. Step 1: Understand autoload behavior

   The anonymous function registered with spl_autoload_register includes the file named after the class plus '.php'.

2. Step 2: Check class and method existence

   Since Car.php exists and defines Car with drive() returning "Driving", the object creation and method call succeed.

3. Final Answer:

   Driving -> Option A

4. Quick Check:

   Autoload loads Car.php, drive() returns "Driving" [OK]

Hint: Autoload includes file; method returns string output [OK]

Common Mistakes:

• Assuming class not found error without autoload
• Forgetting file must exist with correct class
• Expecting no output if method returns string

4. What is the error in this code snippet?

<?php
function myLoader($class) {
    include 'classes/' . $class . '.php';
}
spl_autoload_register('myLoader');

$obj = new User();
?>

Assuming the file classes/User.php does not exist.

medium

A. No error, object created successfully

B. Warning: spl_autoload_register expects a callable

C. Syntax error in function declaration

D. Fatal error: Class 'User' not found

Solution

1. Step 1: Analyze autoload function behavior

   The autoload function tries to include classes/User.php when creating User object.

2. Step 2: Check file existence

   Since classes/User.php does not exist, the include fails (warning) and the class is not loaded, causing a fatal error: Class 'User' not found.

3. Final Answer:

   Fatal error: Class 'User' not found -> Option D

4. Quick Check:

   Missing file causes fatal class not found error [OK]

Hint: Missing file causes fatal class not found error [OK]

Common Mistakes:

• Assuming no error if file missing
• Confusing fatal error with warning
• Thinking spl_autoload_register needs different syntax

5. You have many classes in different folders and want to use autoloading efficiently. Which approach is best to handle this scenario?

hard

A. Use multiple spl_autoload_register calls with random file paths.

B. Manually include every class file at the start of your script.

C. Write a single autoload function that maps namespaces to folder paths and includes files accordingly.

D. Avoid autoloading and use require_once for each class.

Solution

1. Step 1: Understand autoloading with namespaces

   Using namespaces mapped to folder paths allows a single autoload function to locate and include class files efficiently.

2. Step 2: Compare with manual includes and multiple autoloaders

   Manual includes are tedious and error-prone; multiple random autoloaders cause confusion and inefficiency.

3. Final Answer:

   Write a single autoload function that maps namespaces to folder paths and includes files accordingly. -> Option C

4. Quick Check:

   Namespace mapping in autoload = best practice [OK]

Hint: Map namespaces to folders in one autoload function [OK]

Common Mistakes:

• Including all files manually for many classes
• Registering multiple unrelated autoloaders
• Ignoring namespaces and folder structure