SYNOPSIS

DESCRIPTION

Perl has no native representation for booleans. Most of the time the Perl concept of truth is enough. But when dealing with serialization of formats which support booleans, it is desirable to keep the booleans intact on round trips, eg. when writing after loading. And there are other good reasons for that, like strict validation via various mechanisms, like schemas, OpenAPI, type hierarchies, etc.

A solution for that was adopted for JSON modules around 2012 by using references to 1 or 0 blessed into JSON::PP::Boolean which was chosen as the canonical package for these objects.

The problem with that was the coupling with JSON::PP for no apparent good reason. Booleans are independent of JSON and this association makes little sense when loading documents in formats like YAML, MessagePack, BSON, etc. However, the integration of the concept of boolean for all these applications is quite convenient.

Marc Lehmann's Types::Serialiser approached this problem by creating a common interface used by JSON::XS and CBOR::XS modules. This module lifts this core concept (including idea, implementation and documentation) into an isolated treatment for booleans only – so this may work as a common ground for interoperability on booleans as objects for Perl modules.

The implementation keeps the compatibility with the previous agreement on JSON::PP::Boolean by making the Data::Bool implementation stash an alias for JSON::PP::Boolean.

That means

Data::Bool::true->isa('JSON::PP::Boolean');

but also

Data::Bool::true->isa(Data::Bool::BOOL_PACKAGE);

This also allows the optimization of an isa test to a direct comparison of stash pointers. That is,

ref Data::Bool::true eq Data::Bool::BOOL_PACKAGE

is equivalent to

ref Data::Bool::true eq 'JSON::PP::Boolean'

INTERFACE

Data::Bool true values are represented as a reference to a scalar containing 1 – implementations are allowed to directly test for this. For example, one can tell if a value is a Data::Bool true by using this:

Data::Bool::is_bool($value) && $$value

Data::Bool false values are represented as a reference to a scalar containing 0 – implementations are allowed to directly test for this.

METHODS

new

This is similar to Data::Bool::to_bool($value), but "new" produces independent boolean objects while "to_bool" returns the shared "true" and "false" instances.

Most of the time this is not needed or desired, except for a few specialized cases. Prefer "true", "false", "to_bool".

COMPATIBILITY

Besides the agreement on using JSON::PP::Boolean as the canonical package for booleans, as of May 2018, the main JSON modules all step on each others' toes with varying degrees of intensity when it comes to decide what is implemented.

What we consider here the "main JSON modules" are: JSON::PP, Types::Serialiser (used by JSON::XS), and Cpanel::JSON::XS. These are the original sources of ideas, implementations, and package names related to boolean support and the most relevant CPAN modules on the dependency chain.

As these modules are loaded by a Perl program, these actions are all replayed over the JSON::PP::Boolean package. (The last one loaded is basically who wins on the final code at runtime.) This is almost harmless, because their implementations mostly agree with each other. But it is not hard to see this getting out of hand if they start to diverge.

The additional interface for boolean support provided by these modules, whether functions, variables and methods, live on their own packages:

They all have subtle differences related to prototypes, enabled pragmas, and stricter or more lenient behavior. Since those don't dwell in the same base package, JSON::PP::Boolean, they are safe from the point of view of other consumers of booleans and relevant to the back-compatibility history of each of these modules. But they all contribute to the lack of consistency on the interface to deal with booleans.

Those issues mainly stem from the lack of a consensus on ownership of JSON::PP::Boolean.

When Data::Bool gets added to this list as yet another module playing with JSON::PP::Boolean, it takes the most conservative approach: it does not touch a function or overloaded method which is already there. That means it will still provide the entire interface described before, because it will implement anything that is missing. But it may suboptimally accept what has been defined before by a previous module. Moreover it does not fight with modules which get loaded after either.

The best scenario would be if / when the main JSON modules delegated the content of the boolean implementation to a distribution containing JSON::PP::Boolean. Even if that does not happen, this module still offers as a compatible and sane interface to booleans as objects for Perl.

ACKNOWLEDGMENTS

DEBUGGING

When Data::Bool gets loaded, it stops JSON::PP::Boolean module from being loaded, since they are redundant. This prevents subroutines to be redefined and the corresponding warnings. You can set the DATA_BOOL_NICE environment variable to avoid that behavior.

DATA_BOOL_NICE=1

You can set the DATA_BOOL_LOUD environment variable to produce explicit warnings on subroutines found on JSON::PP::Boolean package that Data::Bool will skip and accept as they are.

As a valued partner and proud supporter of MetaCPAN, StickerYou is
happy to offer a 10% discount on all Custom Stickers,
Business Labels, Roll Labels,
Vinyl Lettering or Custom Decals. StickerYou.com
is your one-stop shop to make your business stick.
Use code METACPAN10 at checkout to apply your discount.