Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • If we're still reading blogs and using 32-bit computers in 2038, I'm going to be a very grumpy old man.


    • Some OSes such as FreeBSD/sparc are already using 64 bit time_t's I believe. I'm not sure how badly this affects the ability of software to be ported to them. Mind you, I thought the whole point of having a specific type time_t was so that you coudl redefine it... C. Dontcha just love it.


      • 32-bit int, just say no.

        My next two Perls are going to be 64 bit ... really. Bjorn in perl.dbi.user [] reports "A succesfull 64-bit build of Perl-DBI-DBD:Oracle on IBM AIX 5.2"; I'm going to try building 5.8.6 with DBI and DBD::DB2 shortly. And my other other project is on an Alpha, where the only Perl is 64 bit. (I hope there's a Deb for DBD::MySQL for that platform ;-)

        # I had a sig when sigs were cool
        use Sig;
    • I turn 65 in 2038. So my plan is that I'll be a consultant for the last few years before I retire, rake in a ton of money, and then when the date hits, call it quits.

      It worked for the COBOL programmers, right?
  • Just like the Y2K problem was a problem several years before year 2000!

    I ran into it 10 years ago - in 1994! I had to calculate the date when the client was to be given old age pesion (at 67 years), and sometimes the code failed miserably. It was discovered that it failed whenever the person was born after 1971, as the normal 'time_t' variables overflowed and I therefore assumed that she was very old.

    This was i C++, but the solution was quite simple: port the central parts of Date::Calc to C++ and use tha