in reply to Using timelocal function

Thanks for all the info kyle. Strange isn't it how the ones most polite are the most knowledgable in most cases. Narveson, it's the whole responding to questions with questions and riddled with attitude that makes these discussion groups / forums all the less attractive. The constant questions and lack of an answer doesn't help anybody (i.e. doesn't give me any help and it doesn't make you look any smarter). I normally wouldn't respond in this way but the little jab about posting the example bit is a bit much. I appreciate any help I get in here but if you can't answer a question and all you can do is ask more questions and waste more time with ignorance I'd sooner you don't respond. Thanks again kyle for the friendly and informative responses.

Replies are listed 'Best First'.
Re^2: Using timelocal function
by pc88mxer (Vicar) on Feb 04, 2008 at 22:32 UTC
    rpike, it is not unreasonable to be asked to provide the code you're trying to get to work. It helps explain what you are trying to do, and it's possible that the problem isn't where you think it is. One line of code can equal a lot of words. Moreover, monks have often been known to make other helpful suggestions about coding style, module usage, alternative approaches, etc. when they can actually see your code, so it is to your benefit to post your code and examples.

    In the future, if someone ticks you off I would just ignore them. The worst thing that can happen on this site is to have your posts ignored.

    Concerning your date problem, I would consider using a module that specifically works with dates and not seconds. My favorite module for this is Time::JulianDay. Besides avoiding the timezone issue, there may be problems if you use timelocal with dates before the Unix epoch (1/1/1970).