From @jidanni

perldoc -f hex should say how to convert back too.
perldoc -f oct does.
Be consistent, or at least add a hint.

From @davidnicol

okay Dan, how does this grab you?

--- perlfunc.pod        Tue Mar  8 12:23:37 2005
+++ perlfunc.pod.new    Tue Mar  8 18:22:41 2005
@@ -2273,7 +2273,8 @@

 Hex strings may only represent integers.  Strings that would cause
 integer overflow trigger a warning.  Leading whitespace is not stripped,
-unlike oct().
+unlike L</oct>. To present something as hex, look into L</printf>, L</sprintf>,
+or L</unpack>.

 =item import

The RT System itself - Status changed from 'new' to 'open'

From @jidanni

D> okay Dan, how does this grab you?
OK I guess. But perldoc -f oct gives an example and you don't.
Wait, perldoc -f sprintf doesn't mention how to "convert back"
from what it produces either...

From @rgs

David Nicol wrote​:

okay Dan, how does this grab you?

--- perlfunc.pod Tue Mar 8 12​:23​:37 2005
+++ perlfunc.pod.new Tue Mar 8 18​:22​:41 2005
@​@​ -2273,7 +2273,8 @​@​

Hex strings may only represent integers. Strings that would cause
integer overflow trigger a warning. Leading whitespace is not stripped,
-unlike oct().
+unlike L</oct>. To present something as hex, look into L</printf>, L</sprintf>,
+or L</unpack>.

Thanks, applied as #24036.

@rgs - Status changed from 'open' to 'resolved'