Cool feature in Flex 2's debugger

Submitted by Falken on
As I run Linux at work, I use the command line 'fdb' tool to debug running Flex applications, and for a long time have been swearing at how it dumps variables, and doesn't let you run public getters:

(fdb) print max
$4 = [Object 1600218345, class='Date']
(fdb) print max.getTime()
Variable getTime unknown
Expression could not be evaluated.

But, today, I typo'ed, and something amazing happened. If you put a single full stop after the name of the object, fdb dumps out the internal variables too !

(fdb) print max.
$5 = max = [Object 1600218345, class='Date']
date = 20 (0x14)
dateUTC = 19 (0x13)
day = 4 (0x4)
dayUTC = 3 (0x3)
fullYear = 2006 (0x7d6)
fullYearUTC = 2006 (0x7d6)
hours = 0 (0x0)
hoursUTC = 23 (0x17)
milliseconds = 0 (0x0)
millisecondsUTC = 0 (0x0)
minutes = 0 (0x0)
minutesUTC = 0 (0x0)
month = 3 (0x3)
monthUTC = 3 (0x3)
seconds = 0 (0x0)
secondsUTC = 0 (0x0)
time = 1145487600000 (0x10ab461a980)
timezoneOffset = -60 (0xffffffffffffffc4)

Works with custom objects to:

(fdb) print rec.
$6 = rec = [Object 1599222929, class='com.xxx.yyy.zzz.vo::ChargesVO']
_1413853096amount = 250 (0xfa)
_1724546052description = ""
_3076014date = null
_425188518costCode = "AAAA"
_558842081vatAmount = 43.75
_bindingEventDispatcher = [Object 1593906169, class='flash.events::EventDispatcher']
amount = 250 (0xfa)
costCode = "AAAA"
date = null
description = ""
vatAmount = 12.34
Sections
Flex