Hi!
Any reason why DateTime doesn't have a constant for RFC2616 (HTTP) date
format? RFC1123 and 'r' are _almost_ there but 2616 explicitly states TZ
must be "GMT" and 1123 format produces + instead.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900
On Thu, Sep 30, 2010 at 16:44, Adam Harvey wrote:
> Well, while I'm sending e-mails...
>
> Unrelated to the Comparable RFC, are there any objections to adding a
> function that simply wraps compare_function()? It's depressingly
> common to end up writing a construct like the following in compariso
On 10/01/2010 12:26 AM, Stas Malyshev wrote:
Hi!
Can we make it an operator-like (is_a for example) instead? It
could be more efficient.
Operator has a downside that you can't pass it as a parameter. We
could have something like <=> (spaceship operator!) or even cmp
though :)
OT: Stas, coul
hi Adam,
Thanks for writing and updating a RFC, always the best way to propose
new features :)
On Fri, Oct 1, 2010 at 10:38 AM, Adam Harvey wrote:
> On 30 September 2010 21:33, Adam Harvey wrote:
>> I've just written an RFC (with a patch against trunk) to implement a
>> Comparable interface sim
On Fri, 01 Oct 2010 09:38:19 +0100, Adam Harvey wrote:
On 30 September 2010 21:33, Adam Harvey wrote:
I've just written an RFC (with a patch against trunk) to implement a
Comparable interface similar to that in Java — in effect, allowing
object instances to be compared with semantics defined
On 30 September 2010 21:33, Adam Harvey wrote:
> I've just written an RFC (with a patch against trunk) to implement a
> Comparable interface similar to that in Java — in effect, allowing
> object instances to be compared with semantics defined in userspace.
> This is admittedly at the lower end of
