---
name: "Jifty::Module::Pluggable"
section: "3pm"
platform: "linux"
package: "libjifty-perl"
version: "1.10518+dfsg-2"
release: "Debian 7 (Wheezy)"
platforms: ["linux"]
url: "https://new.carta.tech/Jifty::Module::Pluggable"
---

# Jifty::Module::Pluggable(3pm)

Jifty-specific helper for Module::Pluggable

## NAME

Jifty::Module::Pluggable - Jifty-specific helper for Module::Pluggable

## DESCRIPTION

A custom subclass of Module::Pluggable to override the `"require"` mechanism with one that better fits our own view of the world.

### require

```
    Date:   October 24, 2006 12:19:31 AM PDT
    From:     simon@thegestalt.org
    Subject:    Re: Module::Pluggable and CORE::require
    To:       jesse@bestpractical.com
```

On Mon, Oct 23, 2006 at 09:11:22PM -0700, Jesse Vincent said: does this thread make any sense to you? It looks like Module::Pluggable is interacting poorly with UNIVERSAL::require?

Module::Pluggable used to to use UNIVERSAL::require but I switched because I was trying to get rid of dependencies.

I farmed the requiring stuff off to it's own \_require method in order to make it easy to subclass so that people could override how the require was done.

*But Simon is lying...*

What we actually need to override is Module::Pluggable::Object::\_require, which we do below.