Perl has some special constants that it returns as true and false in response to comparisons and some other boolean expressions. You can peek at the internals of these constants using Devel::Peek:

$ perl -MDevel::Peek -e'Dump(1 < 2)'
SV = PVNV(0xa1046e4) at 0xa102520
  REFCNT = 2147483644
  FLAGS = (PADTMP,IOK,NOK,POK,READONLY,pIOK,pNOK,pPOK)
  IV = 1
  NV = 1
  PV = 0xa1055d0 "1"\0
  CUR = 1
  LEN = 12
$ perl -MDevel::Peek -e'Dump(1 > 2)'
SV = PVNV(0x947a6d0) at 0x9478510
  REFCNT = 2147483647
  FLAGS = (PADTMP,IOK,NOK,POK,READONLY,pIOK,pNOK,pPOK)
  IV = 0
  NV = 0
  PV = 0x947a6c8 ""\0
  CUR = 0
  LEN = 12
[download]

Interesting observations:

• Note the high REFCNT; this ensures that these constants are never destroyed by the garbage collector.

• The PV shows you how these constants are stringified. True becomes "1" and false is the empty string.

• The IV shows you how these constants are converted to integers. True becomes 1 and false is 0.

• They're read-only...

  $ perl -e'$x = \(1 < 2); $$x++'
  Modification of a read-only value attempted at -e line 1.
  [download]

I'm not going to say that these constants are never going to change (never say never!) but it would probably break a lot of code if they did, so I think p5p would be pretty wary of changing this. The Enterprise operator (see perlsecret) relies on them numifying as 0 and 1.