JuniorTheoryCommon

What does the program print?

PHP

<?php

class OutOfStockException extends RuntimeException {}

try {
    echo 'start ';
    throw new OutOfStockException('need 3');
} catch (RuntimeException $e) {
    echo get_class($e), ': ', $e->getMessage(), "\n";
}

start OutOfStockException: need 3

Expecting catch (RuntimeException $e) to miss a subclass: a catch accepts the class it names and every class that extends it, so OutOfStockException is caught.
Expecting get_class($e) to give the class written in catch: it gives the class of the object that was thrown, here OutOfStockException.

Why declare OutOfStockException at all instead of throwing a plain RuntimeException?
In which order should two catch blocks for OutOfStockException and RuntimeException go?

Back to questions Open topic in roadmap →Answer it yourself — Quiz

Back to questions

JuniorTheoryCommon

What does the program print?

PHP

<?php

class OutOfStockException extends RuntimeException {}

try {
    echo 'start ';
    throw new OutOfStockException('need 3');
} catch (RuntimeException $e) {
    echo get_class($e), ': ', $e->getMessage(), "\n";
}

start OutOfStockException: need 3

Expecting catch (RuntimeException $e) to miss a subclass: a catch accepts the class it names and every class that extends it, so OutOfStockException is caught.
Expecting get_class($e) to give the class written in catch: it gives the class of the object that was thrown, here OutOfStockException.

Why declare OutOfStockException at all instead of throwing a plain RuntimeException?
In which order should two catch blocks for OutOfStockException and RuntimeException go?

Back to questions Open topic in roadmap →Answer it yourself — Quiz