Eric J. Roode wrote:
I can barely read XS, so I don't know whether this is a bug in Wx::DateTime or the underlying wxDateTime.
It's a bug in the wxPerl wrapper for Set() method (and all of its overloads). No other wxDateTime methods are affected by this bug.
As you can see, the Set() method does not properly set the Seconds or Millseconds attribute. Also, it seems to be doing something naughty in memory, because when another (larger) program calls Set(), it later crashes; if I change the code to set the attributes individually, it does not crash.
Yes, it is incorrectly freeing the wxDateTime object right after the Set() call returns.
Regards, Mattia
