• BWill (unregistered)

    Frist comments.

  • Brian Boorman (google)

    How many people tried pressing on the "1 Comments" to get to these comments?

  • MIKE (unregistered)

    Maybe I'll go to watch the movie. I'm going to be disappointed if the titular protagonist doesn't have a big archive of her musical performance on DAT, open reel, musicassette or Elcaset.

  • Michael R (unregistered) in reply to Brian Boorman

    Yes

  • (nodebb)

    So, -460°F correspond to 0 Kelvin. The Ice part is solved. But wtf behind the heat?

  • Anonymous') OR 1=1; DROP TABLE wtf; -- (unregistered)

    7.902107851674265e+24 °F equals to 4.3900599175968137e+24 °C. When stored in a 4-byte IEEE-754 floating-point value, that Celsius value is represented as 0x68686868, which is a very curious bit pattern. I think the most likely explanation is that it's ASCII character data for "hhhh" that got misinterpreted as a float.

  • Conradus (unregistered) in reply to Brian Boorman

    (Raises hand sheepishly)

  • Long Time Lurker (unregistered)

    No address given for the movie? No problem, just call them at 212-000-0000 and they'll give you directions.

  • (nodebb)

    Secnod!

    Hey, wait.

  • (nodebb) in reply to BernieTheBernie

    The bogus highs appear to equate to about 0x3A1A1A000000000000000 K. Where that particular amount comes from, who knows.

  • (nodebb)

    I don't see what the problem is with the Theatre advert. It's easy enough to telephone to find their address, although I don't know how they managed to get that number.

  • (nodebb) in reply to BernieTheBernie

    That "inside a supernova" temperature looks similar to the maximum positive value for a Decimal type in .NET, but my memory could be failing me.

  • WTFGuy (unregistered)

    @Nutster It's close. Ref https://learn.microsoft.com/en-us/dotnet/api/system.decimal?view=netframework-4.8

    The max exponent for a .Net Framework Decimal type is 28 and the leading digits of the min/max mantissa expressed in decimal are 79228 ...

    Which leads me to suspect you're on the right track and it's the max Decimal value in some other language / machine with slightly different bit-level details.

  • Yikes (unregistered)

    My guess is something can't read new values into a spot in memory and is providing the same garbage memory value over and over.

  • Nick (unregistered)

    I just want to know how Lyle got to “7th August ‘23” from “23:59 20/07/2022”. I can’t tell if they’re being serious, or mocking the counter-intuitive date formatting that is used by default in the States of United America.

    Even if it was a US format, that’s still a WTF, given that Lloydspharmacy is very much a UK company.

  • recycledevice (unregistered)
    Comment held for moderation.
  • (nodebb) in reply to Nick

    I just want to know how Lyle got to “7th August ‘23” from “23:59 20/07/2022”.

    Read it as the 7th day of the 20th month of 2022 and you get …?

  • Strahd Ivarius (unregistered) in reply to Gurth

    then you get a "month not found" error, usually

  • (nodebb)

    A Java SimpleDateFormat will happily give you 7th August 2023.

    Try it yourself at https://javadevtools.com/simpledateformatparse. Try throwing in some negative numbers as well, it's fun!

  • Donald Klopper (google)

    Lloyds is clearly British from the screenshot only. There are other date display conventions outside of the USA you know.

  • Erk (unregistered)
    Comment held for moderation.
  • (nodebb)

    thanks for info

    Addendum 2024-02-25 19:54: Attention, fellow enthusiasts! I've recently stumbled upon a website that not only provides access to an extensive array of cinematic wonders but does so with a meticulous focus on accessibility and user-friendly design. Navigating through its virtual soap2days corridors is not just a means to find entertainment; it's a seamless and enjoyable journey that ensures the magic of movies and TV series is accessible to everyone, irrespective of their technological prowess.

Leave a comment on “Fire and Ice”

Log In or post as a guest

Replying to comment #583517:

« Return to Article