<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Refactor Imap_Client_DateTime</title> 
  <pubDate>Fri, 10 Apr 2026 17:02:38 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/11074</link> 
  <atom:link rel="self" type="application/rss+xml" title="Refactor Imap_Client_DateTime" href="https://bugs.horde.org/ticket/11074/rss" /> 
  <description>Refactor Imap_Client_DateTime</description> 
 
   
   
  <item> 
   <title>Now that we require PHP 5.3 and DateTime supports serializat</title> 
   <description>Now that we require PHP 5.3 and DateTime supports serialization, most of Imap_Client_DateTime may be obsolete.</description> 
   <pubDate>Tue, 13 Mar 2012 17:36:11 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11074#t70706</link> 
  </item> 
   
  <item> 
   <title>I was looking at this yesterday.  The only issue comes with </title> 
   <description>I was looking at this yesterday.  The only issue comes with the fact that internally in this object it is doing things like fixing common parsing issues with bad dates.  It&#039;s probably cleaner to do this when instantiating the object rather than having a utility function return a DateTime object.

We might be able to optimize by moving the date checking code into the constructor though.</description> 
   <pubDate>Tue, 13 Mar 2012 18:38:05 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11074#t70708</link> 
  </item> 
   
  <item> 
   <title>This was resolved months ago:

commit 52c482d03fa2df9975d5</title> 
   <description>This was resolved months ago:

commit 52c482d03fa2df9975d54887d8f245cb72851ad0
Author: Michael M Slusarz &lt;slusarz@horde.org&gt;
Date:   Tue Mar 13 13:20:45 2012 -0600

    [mms] Horde_Imap_Client_DateTime is now a wrapper around the native PHP DateTime obejct.</description> 
   <pubDate>Mon, 10 Sep 2012 14:37:16 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11074#t72838</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
