Re: standard asynchronous deferred-to-result syntax RFP

2005-07-15 Thread Matt Sergeant
On 14 Jul 2005, at 13:16, David Nicol wrote: I have uploaded asynchronous::universal::ready and asynchronous::universal::set_callback to CPAN. They are both entirely trivial packages with a mess of documentation. The idea behind them is to support asynchonous frameworks in which the immediate

Re: AGAINST RFC 48 (v1) Replace localtime() and gmtime() with da

2000-08-08 Thread Matt Sergeant
On Mon, Aug 07, 2000 at 01:44:28AM -0500, Jonathan Scott Duff wrote: On Sun, Aug 06, 2000 at 11:07:02AM -0700, Russ Allbery wrote: Basically, you don't want to go anywhere near this mess; it eats people. I agree. I see two reasonable options to

Re: AGAINST RFC 48 (v1) Replace localtime() and gmtime() with da

2000-08-08 Thread Matt Sergeant
On Tue, 8 Aug 2000, Nathan Wiger wrote: While I think Time::Object is a really great module, and following these discussions I'm thinking of adding a date() function to it Aaah! Please don't. :-) Name it something else, por favor (or at least wait until this is finalized and make the

Re: date interface (was Re: perl6 requirements, on bootstrap)

2000-08-03 Thread Matt Sergeant
On Thu, 3 Aug 2000, Hildo Biersma wrote: Reply I'd either leave that as (localtime)[3,4,5] (please read the man page for Time::Object), or understand that there's absolutely no need to separate off the variables like that in an object oriented interface: Ah, but we could make the