Re: Time core object and localtime() again

2000-08-22 Thread Jonathan Scott Duff
On Tue, Aug 22, 2000 at 06:31:14PM +0200, Markus Peter wrote: > Well - after all it's just an implementation detail... My question is what's > wrong to only supply the information on perl ports where systems do not > have zoneinfo ? But I've to admit that I don't really care as long as we > fina

Re: Time core object and localtime() again

2000-08-22 Thread Markus Peter
--On 22.08.2000 12:18 Uhr -0400 Chris Nandor wrote: > Yes, well you did say, "In my opinion there's no reason for localtime or > gmtime to be in the core at all." I guess that doesn't necessarily mean > it should be removed in your opinion, but it sure seems like it. As I said - my mail was eas

Re: Time core object and localtime() again

2000-08-22 Thread Chris Nandor
At 17:44 +0200 2000.08.22, Markus Peter wrote: >--On 22.08.2000 11:18 Uhr -0400 Chris Nandor wrote: > >> If there's a good reason to remove localtime(), then fine. But please say >> something more than "web applications don't need it." > >Well, I did not really talk about removing it - I know abo

Re: Time core object and localtime() again

2000-08-22 Thread Markus Peter
--On 22.08.2000 11:18 Uhr -0400 Chris Nandor wrote: > If there's a good reason to remove localtime(), then fine. But please say > something more than "web applications don't need it." Well, I did not really talk about removing it - I know about the backwards compatibility issues. I know my mail

Re: Time core object and localtime() again

2000-08-22 Thread Chris Nandor
At 6:43 +0200 2000.08.22, Markus Peter wrote: >In my opinion there's no reason for localtime or gmtime to be in the >core at all. I can think of two outstanding reasons for them to be in the core: because they've already been there, and there is no reason to take it out. >I especially want to f